Slashdot Log In
100 Years of Grace Hopper
Posted by
CowboyNeal
on Sat Dec 09, 2006 11:32 AM
from the beautiful-jumping dept.
from the beautiful-jumping dept.
theodp writes "Grab your COBOL Coding Forms and head on over to comp.lang.cobol, kids! Yesterday was Grace Hopper's 100th birthday, and many are still singing the praises of her Common Business-Oriented Language."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Women (Score:5, Funny)
I couldn't resist.
Re:Women (Score:5, Insightful)
Men have Perl: a series of unintelligable grunts.
Parent
Re:Women (Score:4, Interesting)
I used to live in the same apartment complex as her in Pentagon City. The owner built a small park in her honor, but the memorial plaque does not mention COBOL or bugs. I suppose out heroes cannot be perfect.
Parent
Re: (Score:3, Interesting)
I was lucky in school to meet Captain Hopper (Captain Cobol - she was promoted many times later.). In 1979 Captain Hopper visited my university, then ETSU and now TAMU Commerce, bringing her loop of microsecond wire. The computer club that night had a drink session for my one and only time as bartender and I served Ms Hopper a drink. Also there was Gary Shelley of "Structured Cobol"
Happy Birthday to You! Happy Birthday to you! (Score:3, Funny)
Kids: Learn COBOL, stay employed (Score:4, Insightful)
COBOL programmers are retiring fast, in 5-10 years expect a mini-boom for this skill set as those who didn't migrate before Y2K decide it's finally time.
Re: (Score:3, Insightful)
(when you mentioned 5-10 I just couldn't resist
Learn novice: be one with the Tao (Score:3, Funny)
Re:Kids: Learn COBOL, stay employed (Score:5, Funny)
Parent
Re:Kids: Learn COBOL, stay employed (Score:4, Interesting)
After working at a shop that wrote COBOL compilers for machine translation into C, I can tell you can it is interesting work, but by no means simple. What a lot of people misunderstand is that COBOL can react slightly differently under each IBM OS that was shipped. Writing a lexer/parser is easy, but the memory mapping and statement convolutions in COBOL were down-to-the-bit tricky.
COBOL was a huge exercise in data massaging, where hundreds of lines were used to map data into a structure which then fed a series of output channels, like a printer, screenmaps or files. Throw in a simple set of arithmetic, but apply it in hacker-esque ways to date bits, for example, and you're scratching your head a lot of the time.
I've read all the bashing here, but one must understand that COBOL's perspective of the world was far narrower than today's. Business data was a simple number-crunching exercise, not much further than the trajectory calculations of the earliest digital computers. I have some one of IBM's computer catalogs from 1971, a longwinded tome filled with secretary-models, low-level circuit specifications, and giant machines that would make a great B-movie these days.
Parent
Re: (Score:2)
Re:Kids: Learn COBOL, stay employed (Score:4, Insightful)
Yes, it works. And yes, it works because nobody dares to touch it. Besides, people who praise COBOL often forget that only a small fraction of COBOL code has survived. Most of the bad code has been replaced by code in another languages long ago.
There are far better tools now: Java/C# for business logic, BPEL for orchestration, rule engines, SQL stored procedures to work with large amounts of data, etc.
Parent
COBL Coding Form slashdotted (Score:2, Informative)
The only way... (Score:4, Funny)
My name is Eric Hopper (Score:2, Funny)
And while I'm sadly not related (or perhaps just not very closely related) to Grace Hopper, it's still neat that someone else with that somewhat unusual last name is in computing. :-)
I have a point system for what people think of when I mention my last name:
Re: (Score:2, Funny)
Greetings,
- Hip
Re: (Score:2)
*chuckle*
Re: (Score:2)
And while I'm sadly not related (or perhaps just not very closely related) to Grace Hopper, it's still neat that someone else with that somewhat unusual last name is in computing.
There are 10742 "Hopper" entries in the white pages in the United States. You do not have an unusual last name-- it's just not common like Johnson or Smith. It ranks 827th out of over 88,000 names in the US, more common than Stein, Fitzpatrick, and Nielsen. My last name shows 314 matches, and I know a dozen of them as relatives. I don't even show up in most name databases. I have an unusual last name.
More than COBOL, she coined the term Bug (Score:2, Interesting)
Look at the bottom of this page. [navy.mil]
Transcending the Matrix (Score:4, Interesting)
Practically all of COBOL was replaced by the printf() command. Which is still the ultimate target for most programs written today, even if the printf() is wrapped in some higher level output function. I'm looking forward to all of all database and relations someday residing in a single invocation with a comprehensive, yet simple interface. Probably a flowchart.
Re: (Score:2)
There are aspects of COBOL that are still not available in present day lnguages.
A super simple example is COBOLs ability to perform a pre-process, sort HUGE amounts of data, and then perform a post-process. Now, granted that was how things worked back then and is not done that way today. Today we just split it up into 2 programs and do some kind of sort in the middle, but the point is that COBOL had some
Re: (Score:2)
I learned BASIC, then 6502 Assembly, then Pascal to get on the timeshare, then DCL, then forth, then COBOL to stay on the timeshare, then a dozen others (including CORAL, PL/I, x86 Assembly), then C, then C++, then Perl, then a dozen others (including Java and SQL).
I wish I could do it all with a flowchart. Someday I will.
Re: (Score:2)
Re: (Score:3, Interesting)
I learned COBOL a quarter century ago, when there were still punchcards (mainly punched tape, but still plenty of cards). printf() mirrors the punchcards. And C++ and Perl, for example, are highlevel languages that still use the grid.
A truly highlevel language would present APIs independent of the underlying HW artifacts. Not jus
Article is misleading (Score:2)
Dirty Rotters! (Score:2)
Perfect Example (Score:2)
Re: (Score:2)
It is very tough to find good COBOL people now... (Score:5, Interesting)
Today, there are still COBOL jobs advertised, and they largely go unfilled. It could have something to do with the fact that there are so few people remaining with the skills, and something to do with the fact that many of them are with banks who are notoriously cheap on IT salaries. The few remaining good COBOL people on the market go into contract positions that usually begin at about $70/hour. I kid you not.
It's a lot of typing, writing COBOL, and the code is at times boringly simple, but if someone is out of work and seriously looking for an IT position, learning it would not hurt. I predict there will still be some call for it 20 years from now.
Re:It is very tough to find good COBOL people now. (Score:2)
IMO the language sucks massively and I felt dirty the first time I looked at code, but the prof (Dr. Cummings) makes it bearable (and that's a high compliment considering my opinion of the lang); I like her besides.
right idea, but outdated implementation (Score:3, Interesting)
The best designed language overall is probably still Smalltalk: it's easy to read, easy to learn, and was designed from the ground up with the idea of being used in an interactive programming environment. It also strikes a better balance between verbosity and expressiveness. Just about the only thing that Smalltalk got wrong was to use strict left-to-right evaluation for arithmetic expressions; a better compromise might have been simply to require arithmetic expressions to be fully parenthesized.
Re: (Score:2)
That is because Smalltalk doesn't have arithmetic expressions - it only has sending messages to objects:
2 + 3
is sending the message '+' to the object '2' with the argument '3'.
Introducing the idea of actual arithmetic expressions into Smalltalk would make it far more complicated.
"amazing grace" indeed (Score:4, Insightful)
more girls - and hell, more boys for that matter - need to learn about people like her.
Re: (Score:3, Interesting)
Ahhhhhh yess... (Score:3, Funny)
Re: (Score:2)
"I love the smell of COBOL in the morning"!
My first computer related job. (Score:2)
COBOL, LISP, FORTRAN (Score:4, Interesting)
Re: (Score:2)
Re: (Score:3, Informative)
First of all, it's John W. Backus not Alan Backus. On the timeline here, the "5 computers" prediction was made by an IBM chairman in 1943. Even long before there was computer languages as such (Fortran 1957, Lisp 1958, COBOL 1959), there was orders of magnitude more than 5 computers. No
Want to live forever? (Score:2)
Learn Cobol! It's the only way to live forever.
You see, in the future mankind will have the ability to revive deceased people. That's why so many of those future-nuts have their bodies frozen: they think they'll be revived. But why would the people in the future do that? It's bound to be expensive, and it's not as if there will ever be a people shortage.
That's why you should learn Cobol. To be irreplaceable not just now, but also in the year 9999. And in the year 99999. And in 999999...
Learn Cobol, for j
Snatch the pebbles from my hand, Grace Hopper (Score:2)
That's ADMIRAL Grace Hopper to you... (Score:2, Interesting)
http://www.hopper.navy.mil/Page.htm [navy.mil]
Ben
COBOL = (Score:3, Funny)
That said, I work in a company which still runs a lot of COBOL code - a bank, funnily enough. I think banks are about the only people still using code written in the 70s *sigh*
Re: (Score:2)
Re: (Score:3)
>written in the 70s *sigh*
Not at all. Many serious users are still using code written in the late 50 and 60's. It's very common in the aerospace industry. Physics and mathematics hasn't changed since then, and some of of the code I see is FAR BETTER (clear, readable, and rigorously accurate) than most C++. We even have the original card decks for some of our stuff (although its been saved in files at this point). Ou
It's easier to ask forgiveness... (Score:4, Informative)
Didn't know that she said that.
I have been quoting this for years. This is precisely the way to deal with any bureaucracy. Asking for permission is the most ridiculous thing to do when wanting to get something done. You are condemning yourself to days and weeks of memos, email, meetings, and PowerPoint charts. Better to just do it and get it done. Cut that Gordian knot. What a useful method of dealing with middle management.
I just didn't know that she was the one who said it first.
Admiral Nanosecond (Score:4, Interesting)
For example, for a 3GHz CPU (.33 nanoseconds per clock cycle), electricity can only travel 10cm in one clock cycle. It's amazing that CPUs can do complex arithmetic when electrical signals inside the chip can only travel 10cm in that amount of time. Wonder why the CPU stalls when there's an access to main memory? Just look at your motherboard and gauge how far your memory is from the CPU, distance alone explains 4-5 clock cycles of the total delay.
Met her 20 or so years ago - remember it well (Score:4, Interesting)
She did NOT create COBOL (Score:3, Interesting)