3 ms·
Easier now...but not necessarily always better. When you read Walter's FORTRAN code from ~1978, keep in mind the environment in which he wrote that code and ed
by tzs 5y ago
Easier now...but not necessarily always better.
When you read Walter's FORTRAN code from ~1978, keep in mind the environment in which he wrote that code and edited it.
Most likely it was all typed in and edited on a Lear Siegler ADM-3A [1] terminal. Depending on when the code was written that terminal would have been running at either 1200 bps or 9600 bps [2]. That's a 24x80 ASCII terminal that may or may not have supported lower case (lower case was an option on the ADM-3A and not all of Caltech's had it).
There were maybe 20 terminals in the terminal room that most students used. There was no scheduling or reservation system. You just had to go there and see if there was a free terminal. (I seem to recall there was a rule that people doing actual class work had precedence over people just doing their own thing, and there was a rule against games during the day [3]).
For actually editing code I don't know what editor Walter used, but it probably was not a screen oriented editor. Most of us used TECO [4].
With the competition for terminals, and line or character oriented editors instead of screen editors, you tended to do most of the thinking about your program away from the computer at least for medium or large programs. You got it all designed in your head (or on paper), worked out most of the details, and then at the terminal it was mostly more typing than programming.
Nowadays with no more competition for computer access and bigger screens with editors that show much more code (and with much more powerful navigation features) we don't need to put nearly as much upfront thought in to our code. For most things that is fine but for some problems figuring it all out in your head first would be better, but I think a lot of programmers no longer learn how to do that.
[1] https://en.wikipedia.org/wiki/ADM-3A https://en.wikipedia.org/wiki/ADM-3A
[2] All the ADM-3As in the computing center at Caltech were 1200 bps when I got there in 1977. Sometime later the operators accidentally configured one to 9600. We users asked if we could have them all changed, and they did so.
[3] But that rule was against playing games during the day, not writing games during the day. Testing and debugging a game during the day was unclear.
[4] https://en.wikipedia.org/wiki/TECO_(text_editor) https://en.wikipedia.org/wiki/TECO_(text_editor)
- zozbot234 5y agoThe lack of lowercase and symbols on some terminals is why languages in the Pascal and Ada tradition are case insensitive and eschew some ASCII symbols, even today. You can even trace some of the weird syntax in COBOL like DIVIDE N INTO X to similar concerns. > You got it all designed in your head (or on paper), worked out most of the details, and then at the terminal it was mostly more typing than programming. Very true, and people would even use pre-formatted "coding form" paper back in the day, to ease that hand-coding process further. It was just hard to do real interactive development while working at a hardcopy terminal, so smart 'glass teletypes' with actual full-screen editing were a significant innovation.
- jes 5y agoYou’re right about preprinted coding forms. I wrote a lot of code in Ryan-McFarland COBOL in the late 70’s, and used coding pads I bought at the college bookstore. In some companies, coding forms were sent to keypunch operators. They took your input forms and punched them quickly and accurately onto 80 column punched cards for you.
- WalterBright 5y agoYou nailed it. I used TECO, first on the DECWriters (which printed on paper) and later on the ADM-3A's using TECO with a TECO macro that turned it into a screen editor. My editor today (microEmacs) is really not much different from that. A couple ASR-33s were available, but I wouldn't use them as they were soooo slooooooow. There was a Tektronix terminal with the green screen storage tube, too, but being a storage tube made it unsuitable for screen editing and playing Empire. I'd often print a listing, and take it back to the dorm and go over it with a pencil making changes that I'd later type in. I usually was at the Jorgenson computer center in the wee hours of the morning when terminals were available and the PDP-10 wasn't slowed to glacial speeds by everyone else using it. On Christmas vacation, I'd fill spiral notebooks with handwritten code I'd type in when I got back to campus. I don't write code in pencil anymore, but I often do work it out in my head while jogging. I don't recall when lower case was available, but Empire being all in upper case certainly suggests it was not when I wrote it.