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.
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.
I had something similar happen with a DCL script.
It was very strange, like the script would run, and then the system would try to execute the output.
There was no way it could happen. I had to delete and rewrite the file.
Sometimes I miss programming in PostScript, the language that, so long ago, gave me my technical "fifteen minutes of fame:" it's like Lisp with a stack, and RPN, welded to a very powerful vector based graphics engine.
PostScript's control of namespace lookup by an explicit stack of Dictionaries is very cool. Like Lisp, or other interpreted languages with a full REPL, turning text to code, and the reverse, was easy.
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
I have always programmed in C++. Except for a stint before it came out when I purchased UCSD Pascal for $100. You got the source code too. Its 16-bit byte codes ran on an interpreter whose idea was later later adopted by Java and Microsoft's reaction to Java, C#. You could debug UCSD Pascal both forwards and backwards, something Visual Studio is still dreaming about doing.
I used many different languages to some extent (some pretty obscure) in my 50+ year programming career. Of them all I think I liked C most of all. It was a short step up from the assembler to learn and was easy for me to use. Being a control freak I felt it gave me the best product from my time. I found the C lib functions straight forward and manageable.
This is just an old fart's opinion. I can get by in just about anything. There is truly nothing under the sun. The language syntax and organization changes but it is all pretty much the same.
Last Visit: 16-Nov-19 15:50 Last Update: 16-Nov-19 15:50