Most of my friends are coders. All of them have the mentality that they are in it for the money. They end their shift and they don't code a single line more until the very next day. While at work, the goal is to fulfill assigned tasks within the deadline so the boss is happy - if they have to throw a horde of libraries at a problem then that is acceptable unless the project manager complains.
Re: Re: Cobol/gnucobol
By: Jcurtis to nelgin on Fri May 30 2025 08:11 am
Not without tighter moderation. Most people won't put up with Troll Personality Disorder. All it takes is one to spoil the fun.
I would take six hundred MROs than a single RPGnet moderator.
The reason is simple. Trolls you can deal with. A single asshole moderator means the platform becomes worthless.
In fact I would argue that the strength of alternative nets is that it is
I would argue that the strength of alternative nets is that it is not
held hostage by a single moderator or operator.
I would argue that the strength of alternative nets is that it is not
held hostage by a single moderator or operator.
Their users are a tiny minority. Don't look strong to me.
I coded on iSeries professionally.
That's amazing! Many years ago, second half of 90s, I was at the
AS/400 support center. Unfortunately I probably wasn't savvy enough
to learn COBOL on AS/400. it felt so difficult back then.
I think I have a book on COBOL on AS/400 in the garage that I have to
get back to life. I was much enjoying networking.
Just to set the expectations, I'm writing a simple app to catalog some collectables. It has a single indexed file at the moment.
It wasn't what I meant, but you actually answered me in the example
you provided.
What I meant was something like:
"(A)dd, (E)dit, (D)elete, (E)xit => _"
In your example code was stored in the variable PROCESS-INDICATOR
It was! But there's so much to learn.
At the end, I just want to have a bit of fun.
That and the Russians would certainly have caught the US faking it. They would have been able to tell if nothing went up.
Do you think the use of the virtual keyboard has significantly changes how people compose their replies? In that they just write shorter, disjointed comments?
I was being sarcastic.. I tend to think it was more plausible that we did rather than faking it.
I just saw a video where a jailbroken Kindle can run Linux and act as an e-ink SSH console. That's my next project. that might support a
bluetooth keyboard...
Though the Windows one is also electron.
Back in the 80s coders were developing games using straight opcodes with no assembler nor nothing because if you used high level languages people would complain about performance.
Today, the people paying does not give a damn, therefore the people who codes does not either.
Re: Re: Cobol/gnucobol
By: poindexter FORTRAN to Nightfox on Sat May 31 2025 10:24:12
I just saw a video where a jailbroken Kindle can run Linux and act as an
e-ink SSH console. That's my next project. that might support a bluetooth
keyboard...
Very interesting. Got a link to the video?
Very interesting. Got a link to the video?https://github.com/Wint3rmute/arch-linux-on-kindle
I just saw a video where a jailbroken Kindle can run Linux and act as
e-ink SSH console. That's my next project. that might support a blueto
keyboard...
Things were a lot different back then. Programs were much smaller, less complicated, needed fewer resources, simpler architechure. Comparing then and now is like comparing a Volkswagon Beatle to a Tesla Model S.
There were indeed assemblers back then. I used one on a PET 8032 for my 6502 Machine Language class in college back in '80-81. Also, assemblers don't deal with high-level languages, just machine language.
From a coding perspective, unless the client is a data center or some such, the end-user shouldn't have to care. All that matters is they get a product that works as advertised.
The customer should care because when the developer decides to pull a library with 300 dependencies instead of writing half a dozen custom funtions he is forcing the customer to buy more RAM. When the developer uses a bad library that causes excess IO he is forcing the customer to upgrade his storage or networking gear. Basically, new school developing consists on passing on the expenses of inefficiency to the customer. It works because customers suck and deserve to die.
Once upon a time, I considered writing a program to do something like that with my model railroad equipment. I eventually figured out that keeping it all in spreadsheets with gnumeric was sufficient enough. ;)
One thing that some people have difficulty with when going from
another language to COBOL is that, although the code reads like English, they are not used to needing to define all of their variables in working storage. For some reason, that just seemed logical to me.
Once upon a time, I considered writing a program to do something like tha
with my model railroad equipment. I eventually figured out that keeping i
all in spreadsheets with gnumeric was sufficient enough. ;)
Well, to be honest, part of the plan was to make a comparison like
"the cobol/mainframe way" and "the unix way", i.e. using standard shell
tools to manipulate CSV. I found out sc-im as a terminal based spreadsheet.
Ages ago, in 1999, my mentor invented the noSQL term (you can search him on wikipedia).
It was based on shell only, using sed awk and other standard
tools. I wrote an extended article about it on Linux Journal. Although
I can't recall much, I have a grasp on how powerful shell could be.
Plus, I recently joined the FreeBSD bandwagon. I truly admire how some FreeBSD have mastery on shell. If you look at the CBSD management tool
source code, feels like reading C++ instead of shell. Kudos to them.
I know, a csv/ods/xls can be as powerful today, aka "the poor man's database", but it was an excuse to learn COBOL.
Also, I am a model railway lover, although I lack the space and time
so I just had a few models of the (real) trains I used to play with
when I was a kid. My father used to work for the local railway company,
so I was not an estranger to it.
One thing that some people have difficulty with when going from
another language to COBOL is that, although the code reads like English, they are not used to needing to define all of their variables in working storage. For some reason, that just seemed logical to me.
I don't feel that as a huge issue for me. Many languages need to define
the variables at the beginning. It's just in a separate section.
I'm much more dealing now with the limits of the programming language,
as many things aren't built-in. Ex. generating a random string is not
as straightforward as I'm used to. But I get it, it was a language
that was born in the 60s, a lot of stuff just wasn't there.
Dumas Walker wrote to DARKNETGIRL <=-
I have tried BSD out a couple of times, usually just to test/play with
on a second-hand machine, but have always stuck with linux. I would
say that, too me, it seemed too similar in some ways to motivate me to change.
I've wanted to go back to a BSD for a more old-school desktop OS, been
tempted to look at NetBSD.
If you do, I am interested to hear of it. I wonder if they still support 386 CPUs. I think linux quit those.
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
Re: Re: Cobol/gnucobolI used to run NetBSD a long time ago. A friend of mine was a developer
By: poindexter FORTRAN to Dumas Walker on Wed Jun 25 2025 08:11 am
I've wanted to go back to a BSD for a more old-school desktop OS,
been tempted to look at NetBSD.
If you do, I am interested to hear of it. I wonder if they still
support 386 CPUs. I think linux quit those.
---
� Synchronet � Vertrauen � Home of Synchronet �
[vert/cvs/bbs].synchro.net
If you do, I am interested to hear of it. I wonder if they still support 386 CPUs. I think linux quit those.
I Know Debian and OpenSUSE still support 32 bit processors.
On Thu, 26 Jun 2025 09:38:49 -0700
I used to run NetBSD a long time ago. A friend of mine was a developer
and kept nagging me to use it. I think I tried to go bleeding edge and always ended up with some library incompatibilities. I'm sure things
are better these days. I actually quite liked it but ended with going
back to Linux with it being more the mainstream.
Re: Re: NetBSD
By: nelgin to All on Fri Jun 27 2025 09:21 am
On Thu, 26 Jun 2025 09:38:49 -0700
I used to run NetBSD a long time ago. A friend of mine was a
developer and kept nagging me to use it. I think I tried to go
bleeding edge and always ended up with some library
incompatibilities. I'm sure things are better these days. I
actually quite liked it but ended with going back to Linux with it
being more the mainstream.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
If you do, I am interested to hear of it. I wonder if they still support
386 CPUs. I think linux quit those.
I Know Debian and OpenSUSE still support 32 bit processors.
But which ones. I think the kernel quit 386s.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
If you don't like my style or content, you're not required to read it.
I read it as him paying you a compliment for "pulling it off" and learning it.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
I read it as him paying you a compliment for "pulling it off" and learning it.
I used to run NetBSD a long time ago. A friend of mine was a developer and
kept nagging me to use it. I think I tried to go bleeding edge and always
ended up with some library incompatibilities.
NetBSD runs on more architectures. That's no easy trick. Pulling it off is
impressive. Using NetBSD takes time. It's another world to learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD? I have a pretty good grasp on what it will run on. I find this post pointless.
NetBSD runs on more architectures. That's no easy trick. Pulling it
off is impressive. Using NetBSD takes time. It's another world to
learn.
Why are you telling me what I already know? Didn't I say I ran NetBSD?
I have a pretty good grasp on what it will run on. I find this post pointless.
Why are you telling me what I already know?...
I read it as him paying you a compliment for "pulling it off" and learning it.
I read it as him complimenting NetBSD on running on many architectures and goo
for them. *shrug*
Eh? Sounds to me like he was paying you a compliment ("That's no easy trick. Pulling it off is impressive").
Installing NetBSD on a PC is like installing Linux on a PC.
Re: Re: NetBSD
By: nelgin to All on Sat Jun 28 2025 01:47:34
Why are you telling me what I already know?...
Whoa, dude. Go have a Snickers. ;)
Installing NetBSD on a PC is like installing Linux on a PC.
NetBSD package management takes time to learn. It's not the same as
linux. And you need to compile a custom kernel. The default kernel is bloated with features many users don't need. Editing the kernel config often results in a failed build because you removed some essential dependency. It takes time, trial, and error to get it right.
i didnt need to edit the kernel config ... like years ago
Jcurtis wrote to MRO <=-
i didnt need to edit the kernel config ... like years ago
I did, to make it fit in a small memory system. Do you know what your kernel memory size is?
On modern, "normal" hardware, who gives a shit what the "kernel
memory size" is?
---i didnt need to edit the kernel config ... like years ago
I did, to make it fit in a small memory system. Do you know what your kernel memory size is?
Re: Re: NetBSD
By: Jcurtis to MRO on Mon Jun 30 2025 04:42 am
i didnt need to edit the kernel config ... like years ago
I did, to make it fit in a small memory system. Do you know what
your kernel memory size is?
did you intentionally edit my quote to make it say something else?
NetBSD package management takes time to learn. It's not the same as
linux. And you need to compile a custom kernel. The default kernel is bloated with features many users don't need. Editing the kernel config
often results in a failed build because you removed some essential dependency. It takes time, trial, and error to get it right.
It's not as easy as linux, if you want to do much work with it. Saying otherwise won't make it so.
Re: Re: NetBSD
By: MRO to Jcurtis on Mon Jun 30 2025 11:39 am
did you intentionally edit my quote to make it say something else?
No. I didn't add or change any words. I cut unneeded words. That's trimming, not editing.
---i didnt need to edit the kernel config ... like years ago
No. I didn't add or change any words. I cut unneeded words. That's trimming, not editing.
yeah but you entirely changed my sentence to make it say something else.
why even do that?
you changed it to:
i didnt need to edit the kernel config ... like years ago
Jcurtis wrote to MRO <=-
Re: Re: NetBSD
By: MRO to Jcurtis on Mon Jun 30 2025 08:34 pm
No. I didn't add or change any words. I cut unneeded words. That's trimming, not editing.
yeah but you entirely changed my sentence to make it say something else.
why even do that?
you changed it to:
i didnt need to edit the kernel config ... like years ago
It seemed harmless to me. Sorry for any offense.
you changed it to:
i didnt need to edit the kernel config ... like years ago
It seemed harmless to me. Sorry for any offense.
you're editing people's text to make it something else.
just stay out of it or dont quote it at all.
good to put thought into the overall design, or else you could end up w code that's hard to maintain.
Most software design is trash. That's why normal people don't like computers. ---
Most software design is trash. That's why normal people don't like computers.
Good point! I think you're right about that.
Re: Re: NetBSD
By: nelgin to All on Fri Jun 27 2025 09:21 am
On Thu, 26 Jun 2025 09:38:49 -0700
I used to run NetBSD a long time ago. A friend of mine was a developer
and kept nagging me to use it. I think I tried to go bleeding edge and always ended up with some library incompatibilities. I'm sure things
are better these days. I actually quite liked it but ended with going
back to Linux with it being more the mainstream.
NetBSD runs on more architectures. That's no easy trick. Pulling it off is impressive. Using NetBSD takes time. It's another world to learn.
Most software design is trash. That's why normal people don't like computers.
How long has it been since somebody called you an idiot?
| Sysop: | Gargoyle |
|---|---|
| Location: | Wayne, OK |
| Users: | 19 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 61:16:31 |
| Calls: | 151 |
| Files: | 295 |
| Messages: | 68,964 |