The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Yes, but remember how long it took to write out the coding sheets, get the cards punched, submit them for compilation, only to find you made a simple spelling mistake, or the punch girl mis-read your hieroglyphics.
Yeah, my first job was on an old IBM Series/1, which ran in this somewhat low-level language called EDL (Event Driven Language).
It was kind of assembler-like. Debugging consisted of getting a printout, on the left of which would be the actual compiled code (80A2 as an if-equals, I think).
So, you learned a lot of how memory is actually managed by getting that close to the OS. I think that helps understand (or at least be able to theorize) better about what's under the hood when using higher-level languages.
I wouldn't say I miss it, Bob. But, it was interesting to peer into the sausage factory, and I think it made me better at thinking about doing things (relatively) efficiently in more modern systems.
Fortran 77, I took a Basic class (my first programming class) before this and darn near swore off programming, as the spaghettification factor was overwhelming. A math instructor talking me into taking Fortran class and I loved it.
Motorola HC11 assembler is another one, my first assembler language. At the time Motorola had what I thought was really good documentation regarding the chips' operation and the instruction set, coded a lot of assembler back then.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
I've learned BASIC "programming" (and I use that term loosely) on a Commodore 64. Line numbering, only having the first two characters of variable names being significant, resource limitations of the hardware...the short answer would have to be "no".
I would like to have Turbo Pascal 5.5 and Turbo C on my PC again
me too (specially the turbo C), and I am not that old
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
There are the languages I really liked working in at the time: Ada, VAX FORTRAN, VAX/VMS DCL (scripting), LISP, and Intel assembly language using a flat memory model. At the time I developed sufficient fluency in each of these that I could solve any programming problem you like in them, given enough time.
Interestingly, I don't feel any nostalgia to go back to programming in any of them. The amenities available now in most languages are so superior it's incredible. I know that Ada, FORTRAN, and LISP all have contemporary versions with modern facilities, but those all seem to have a "me too!" flavor to them.
Today my language of choice is C# unless there's substantial bit/byte-fiddling to be done, and then it's C++.
I loved the VAX/VMS system. I used Pascal, some C, DCL, FMS, and others. I had a 2 shelf set of manuals from DEC, which if you followed the rules everything would just work. I even developed a primitive pre-object system where I would pass a structure for specific data entry forms to several routines; saved a lot of coding.