If you pull this off, please market your product on this forum. You'd make a lot of us happy.
Technically Fortran isn't an acronym since it's short for "The IBM Mathematical Formula Translating System)".
So long ago.... I can't even remember any of the COBOL vs FORTRAN programmer jokes. Just everybody smoked a lot. Explains why the IBM Model M has those deep keystem wells. Keeps all the ash out.
[real programmers] have no use for managers. Managers are a necessary evil. They are for dealing with personnel bozos, bean counters, senior planners, and other mental defectives.
Fortran was a bit before my time, but I always liked "God is Real, unless declared Integer". Even before I knew the exact story* behind the joke, I found it funny.
[/i]
Iron, you'll appreciate this - from wikipediaShow Image(http://upload.wikimedia.org/wikipedia/en/thumb/0/07/Fortran_acs_cover.jpeg/150px-Fortran_acs_cover.jpeg)
Technically Fortran isn't an acronym since it's short for "The IBM Mathematical Formula Translating System)".
Predates COBOL by a few years.
I remember the days of smoking at my desk...
Ok, but almost every APL program *can* be written in one line. (joke!)
- Don't use APL unless the whole program can be written on one line.
I'll tell you what, I wouldn't lump Ada in with Pascal (I don't know BLISS but damn it sure sounds familiar). And this is coming from a guy who hates Wirt(less) and Dykstra with a passion and I claim they have done more to destroy high performance computing and screwed up more computer science students than any two buttheads in the history of computing. Ada is one fantastic language. If you wanted to, you could replace every COBOL, FORTRAN, PL/I, C, and C++ program (and more if I had time to reflect on the subject) ever written and not miss anything. About the only thing I haven't seen Ada do is be as easy as COBOL is to generate reports with, just because of the way you can do PIC clauses in a print layout in WS. You can use PIC clauses in Ada (with the right annex support) but it still isn't as easy to bang out a few thousand line report. If you haven't looked at Ada since 83, have a look at it now. Superb!
- Don't use Pascal, BLISS, ADA, or any of those sissy-pinko computer science languages. Strong typing is a crutch for people with weak memories.
Damn, you got that one right!
- Don't drive clapped out Mavericks. They prefer BMW's, Lincolns, or pick-up trucks with floor shifts. Fast motorcycles are also highly regarded.
Yeppers
- Know every nuance of every instruction and use them all in every real program. Puppy architects won't allow execute instructions to address another execute as the target instruction. Real programmers despise such petty restrictions
Even before I knew the exact story* behind the joke, I found it funny.
*(For those who don't know it - In Fortran, variables were automatically typed according the first letter of the variable name, unless explicity defined otherwise. It would so happen that a variable whose name began with G would be a real number variable. Before I read the actual explanation I got the impression that Fortran variables were automatically typed as real unless defined otherwise. Wasn't technically correct, but the joke worked either way.)
Real Programmers...
Small hands, but quick.
How about oil cooled Turing Machines?
We're so OT we're never going back so let me mention this great book on the first uses of computing.
I used to program on an abacus.
Your keyboard is an IBM 3197 termional keyboard, 122 keys.
I think the only way you'll get it working on a PC is through the Keyboard Babel dongle.
Interesting... I was interested in trying to convert a 122-key Model F to be PC compatible. Is there anyway at all of getting Linux to recognize the arrow keys on the keyboard to be recognized?
showkey -s
to see what scancodes the arrow keys produce, and showkey
to see if Linux has mapped them to internal keycodes. If a key reports a scancode but no keycode, you need to use the setkeycodes utility to add them. On my keyboard, for example, I had to do this for the cursor up and right keys:setkeycodes 0x78 103 0x7D 106
keycode 103 = Up
keycode 86 = Left
keycode 106 = Right
keycode 85 = Down
It can be found at my page on the 1390876 (http://www.seasip.info/VintagePC/ibm_1390876.html).Nice page. The SVG images are a little fussy though, Seamonkey 1.1.17 insists on applying my minimum font size to the lettering in the key layout (which does not look pretty); as a workaround, I'd try exporting the text as curves. FF 3.5 does not do that but page scrolling is a little sluggish in both browsers (which is more easily noticed on my machine which hardly sets any records for computing speed these days).
my page on the 1390876 (http://www.seasip.info/VintagePC/ibm_1390876.html).
This is quite interesting. When I disassembled my AT Model F, there were unused contacts that corresponded to scan-codes 70-75 (from your diagram on your page that you linked). When I tried to make them work, they didn't respond, despite the fact that the looked perfectly functional.