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.
Likewise: but mine was even worse, because it used a preprocessor (it was the source for the preprocessor) to provide a "structured programming" approach to FORTRAN called ROOTS[^] - I worked for Rob for six months back in the day as part of my university industrial training.
And I still use the flowcharting methods for software design ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
FORTRAN and COBOL, I can forgive. They were beginning to shape the programming world. Python on the other hand I can not forgive. This is the information age, it supposes to shake off those silliness.
Admittedly no language is perfect. But when I look at some languages I had to scratch me head in disbelieve "What the heck?" Those times it always bring back memory of past Minnesota Governor Jesse Vantura's comments about St. Paul road system "They must've been designed by drunken Irish."
Sort of: it was intended for punch cards, so in the early days specific columns had specific meanings.
I can't believe you mentioned this! You set my therapy back decades!
Funny story: my freshman year of college we submitted programs on punchcards. During the first class of the first course, we were warned to buy a wide marker. Type your deck, line the cards up neatly, then draw a diagonal stripe across the top of the deck. If the deck got out of order the stripe could be used to visually fix the order of the deck. Also use at least 2 rubber bands to hold the deck together, in case one broke.
If we had to make significant revisions to the program, the top could get messy with multiple stripes, but the manual labor of producing a deck made us better, more careful programmers. That and having 12 hour turnaround times on program runs near the end of the semester -- we could not afford to be sloppy at all. [It also made us accurate typists -- miss a stroke, throw out that card]
It's end of the semester and nearing midnight. I had dropped off my deck at noon and had walked across campus to pick up the deck + printout. My run had been successful so I got to sleep!
Guy is walking towards me, carrying a deck of at least 300 cards. He drops the deck, the single rubber band breaks, and cards spray every where. No sign of a stripe on the top of the deck.
Poor guy looks like he's going to cry. He starts to get down on his knees to pick up the deck, straightens up, shakes his head, and walks away ...
At the time I was totally surprised. Maybe shocked.
In later thinking about it -- the guy was an upper classman, based upon personal appearance and the size of the deck (higher level class, longer programs). Everyone was warned to take the aforementioned care of the decks, and the displays for rubber bands and felt-tipped wide markers were right next to the punch cards in the campus store. Freshman knew enough to take care ... upper classmen should know even better.
"Modern" Fortran is a bit better with so-called free-format coding. Intel Fortran even offers Visual Fortran that integrates into Visual Studio. Maybe other compiler makers do something similar. It's not as painful as it once was. Thankfully.
And reveal all the passwords you're trying to enter
And fight with matplotlib over cpu time
I can't count the number of ppl not believing me when I told them that IDLE was causing their problems.
I even made some relaunch code, just to make my Python scripts escape from IDLE's claws
Warning (from warnings module):
File "C:\Program Files (x86)\Python_36\lib\getpass.py", line 100
return fallback_getpass(prompt, stream)
GetPassWarning: Can not control echo on the terminal.
Warning: Password input may be echoed.