¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Real programmers don't write in FORTRAN. FORTRAN is for pipe stress freaks and crystallography weenies. SAYS MY Tk4- COOKIE JAR


 

In all these missives regarding programming languages used et al, no one has mentioned

1. RPG, RPG II (and later)? from IBM 1401 and newer systems.
2. Macro assembler??????? from IBM 1401, 7094, ICL 1501 and 1900's

Now back in the day at one of my first jobs in London as a programmer around 1963 (1401) I had to use machine code (if nothing else then keying in the bootstrap code to start the machine) then after a few months using Assembler then Macro Assembler and then followed by Cobol.?? Note I did do operating on a 1401 in 61 at weekends to earn pin money etc - save having to do a paper round.

Next site / job was ICL 1900's which also had Burroughs and Honeywell along with a lot of UR's (Unit Record systems) and yes serious programming here using short lengths of single wire cable with a baby plug at each end connected to a wide plug board that was the programming method. If you exceeded 10 layers of wire you knew the program was too complex and had to break it down some more.

This cabling was used in 1401 and 360 back boards (instead of modern circuit boards).

Now to help move away from UR systems we used RPG and initially used a UR that had a card reader and punch connected to one of the mainframes acting as input.

Now using RPG the processing could get more complex i.e., beyond read card, basic process, punch output card and create a report.

The Macro assembler was used for the stuff that RPG (and Cobol) could not yet handle and once practised could churn out code very quickly.

Or was it, when I was young :)

Vincent
still only 73 and started young..

On 27/11/2020 18:40, pjfarley3 wrote:

+1, that is a true statement.? Cussing the machine is the one thing we programmers all have in common.

But in response to the original question, I think there is no need for a ¡°favorite¡± language.? In my experience I have written in Fortran (II and IV), COBOL, 360/370/390/z Assembler, PL/1, Rexx, Pascal, SQL, (g)awk, miller (a scripting language), Snobol, Icon (a procedural successor to Snobol), *ix shell scripting, C, Metal C, python, HTML, and even a smidgeon of perl, and that¡¯s not counting the large variety of utility ¡°languages¡± you need to get the rest of the job done (JCL, IDCAMS, IEBDG, Comparex, Insync Compare, CA FileMaster, CMD.EXE scripting, Powershell, etc.).

I think the only major language I never had the opportunity or need to learn was Basic in any of its incarnations.

My ¡°favorite¡± language tends to be the one that gets the task done today, and there is frequently a different language suited to each specific task in each different time period.? Use whatever language is available that works for you, and never stop learning new things.

Join [email protected] to automatically receive all group messages.