|
I recently got pulled in to help out on a 30+ years old mainframe project written in COBOL. It was a bit of shock to realise how much I remembered, since it had been 30+ years since I last worked with COBOL!
I occasionally miss my old FORTRAN days (most recently Fortran 77 rather than FORTRAN IV) but I never have yearned to do COBOL (or even PL/1) again.
Nostalgic thoughts?
- I would love to change the world, but they won’t give me the source code.
modified 28-Aug-19 11:06am.
|
|
|
|
|
I kinda miss Turbo Pascal... Most fond memory of it was that it was only $30.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
$30 Dollars, or a few floppies to the right person at college... I wonder why Borland had troubles $30!
Pascal and it's grown up brother Modula2...
Begin
writeln("hello world")
End. and on...
|
|
|
|
|
$30 was a long way from $1000 for Borland Pascal...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Was there a difference then? I always thought Turbo was the update for 386.
|
|
|
|
|
"Turbo Pascal" with a single manual and 5-1/4 floppy disk became "Borland Pascal" - a monstrosity with four/five manuals and several 3.5 floppies. Along with the change, the cost increased astronomically.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Turbo Pascal was my first thought as well!
|
|
|
|
|
|
Me too ... and I miss Turbo Prolog even more. Of course, everything was simpler those days.
"The only easy day was yesterday" as the Navy Seals say.
|
|
|
|
|
Those were the days... 
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
Still keeping an old TP app alive that I offered to help out with 25 years ago! DosBox and no "Opening the file" messages - joy!
|
|
|
|
|
FoxPro for DOS (pre-MS). I wrote a sales lead tracking application (think early CRM) that ran unchanged for well over a decade. It even survived Y2K. 
|
|
|
|
|
I used FoxPro for DOS at my workplace to create some pretty complicated applications.
Once, during an upgrade to our payroll system used for almost 20,000 employees, I wrote an application to compare the master file output from the old version with the new version, looking for differences which would signal compatibility issues. This app helped to eliminate a lot of confusion and busy work by our HR and payroll folks to ferret out those problems.
My star shone a little brighter for a while...sigh.
FoxPro fan
|
|
|
|
|
It's weird.
I've always programmed in C++ (and sometimes C) in the last 30 years; there was a small stint in pascal at one earlier point, but not enough to be nostalgic.
So, no false nostalgia of better days.
I'd rather be phishing!
|
|
|
|
|
I miss Clarion. Surprisingly, it is still around (I just checked). I used it back in the DOS days.
“The palest ink is better than the best memory.” - Chinese Proverb
|
|
|
|
|
Yup it is still being used. I just created a .net for clarion to use.
[Signature space for sale]
|
|
|
|
|
I Sometimes miss the Univac 1100 Assembler that I spent so many years working on. But most modern languages are so much better in many ways.
|
|
|
|
|
I miss PLAN (Programming LANguage for the ICL 1900 series). Wrote many nice utilities in that.
Still a member of the BCS Fortran SIG, but mainly used FORTRAN IV (and dabbled with F77).
'Modern' (post 1970) languages have added layers of complexity in the guise of simplification.
|
|
|
|
|
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.
|
|
|
|
|
Ah yes - happy days (not). Two weeks turnround. It ensured we did desk debugging properly.
Still got some of my old programs. Has anyone got a card reader?
|
|
|
|
|
Me, too. But also coding for 1900/2903/2960 DME executives where op codes were written in octal. 000 = LDX, etc
|
|
|
|
|
I learned programming in college by writing programs in Algol-60 on a Univac 1108. My, how time flies!
|
|
|
|
|
I learned Assembler, Fortran and PLUS on the 1108. Never got into Algol-60, but I know one of the Burroughs systems used it for all their Operating System code.
|
|
|
|
|
I spent a lot of my life coding in Z80 assembler, and sometimes - but not often - I do miss it.
Being that "close" to the hardware feels ... natural, if you know what I mean.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Griff. We have received complaints from various hardware devices about you not respecting personal space...
This space for rent.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
