Slashdot Mirror


100 Years of Grace Hopper

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."

17 of 184 comments (clear)

  1. Women by Anonymous Coward · · Score: 5, Funny

    It figures. One of the wordiest (is that a word?) programming languages was invented by a woman. Talk talk talk. :-)

    I couldn't resist.

    1. Re:Women by Tablizer · · Score: 5, Insightful

      It figures. One of the wordiest (is that a word?) programming languages was invented by a woman. Talk talk talk. :-)

      Men have Perl: a series of unintelligable grunts.

    2. Re:Women by Vreejack · · Score: 3, Interesting

      She invented computer bugs, too. http://www.waterholes.com/~dennette/1996/hopper/bu g.htm

      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.

      --
      "Will future ages believe that such stupid bigotry ever existed!" -- Ivanhoe
  2. Happy Birthday to You! Happy Birthday to you! by Anonymous Coward · · Score: 3, Funny

    Even though you died in 1992, Happy Birthday to You!

  3. Kids: Learn COBOL, stay employed by davidwr · · Score: 4, Insightful

    Seriously. Learn some legacy skills, you'll need them to help your future employer maintain their legacy stuff or migrate it.

    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.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
    1. Re:Kids: Learn COBOL, stay employed by camperdave · · Score: 4, Funny

      Nonsense! Cobol is machine independent and self-documenting, and it is still around because it is a very fit, if not the fittest, language for business purposes. Besides It would likely be far easier to pull together a COBOL compiler than to rewrite, test, debug, (document, don't forget document) and release any application that was written in COBOL.

      --
      When our name is on the back of your car, we're behind you all the way!
    2. Re:Kids: Learn COBOL, stay employed by mugnyte · · Score: 3, Interesting

      ...pull together a COBOL compiler...

        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.

    3. Re:Kids: Learn COBOL, stay employed by Cyberax · · Score: 3, Insightful

      I helped to maintain COBOL software.

      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.

  4. The only way... by camperdave · · Score: 3, Funny

    The only way I could code my way out of a wet paper bag in COBOL would be if my life depended on it (and I had a few COBOL programming texts in the bag with me). All I remember about COBOL is that it is long winded... as per its alternate acronym expansion: Considered Obsolete Because Of Length.

    --
    When our name is on the back of your car, we're behind you all the way!
  5. Transcending the Matrix by Doc+Ruby · · Score: 3, Interesting

    Someday we'll look back at the rigid grid of orthogonal rows/columns of database tables with the same pity with which we look back the character grids in which we coded COBOL programs.

    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.

    --

    --
    make install -not war

  6. It is very tough to find good COBOL people now... by Panaqqa · · Score: 5, Interesting

    The university I went to stopped teaching it about 20 years ago, and most programmers of COBOL with much in the way of practical real world development experience retired long ago. In fact, a lot of them came out of retirement for a few months or a year prior to Y2K because the money offered was so good.

    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.

  7. "amazing grace" indeed by deitrahs · · Score: 4, Insightful

    one of the few things i have on my "i love me wall" is one of her nanoseconds, framed with a letter from the admiral to my mother (whom she was trying to encourage into a career in computer science). now that i have a daughter of my own, who is already quite geeky herself, i counterbalance the pop culture effect with stories about women like grace hopper.

    more girls - and hell, more boys for that matter - need to learn about people like her.

  8. COBOL, LISP, FORTRAN by Frumious+Wombat · · Score: 3, Interesting

    Be sure to pay homage to the inventors of the other two ur-languages; Alan Backus, and John McCarthy. Without them, we'd still be programming in assembler, and there probably would be only a world-wide market for 5 computers.

    --
    the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
  9. It's easier to ask forgiveness... by ishmalius · · Score: 3, Informative

    "It's easier to ask forgiveness than it is to get permission."

    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.

  10. Admiral Nanosecond by conradp · · Score: 3, Interesting

    Back in high school I attended a talk by Admiral Hopper where she passed around a wire about 30 centimeters long and explained to us "this is how far light, or any electromagnetic signal, can travel in one nanosecond." That illustration has always stayed with me, it helps to explain a lot of the limitations inherent in hardware now that CPU speeds have become so fast.

    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.

    --
    "To be absolutely certain about something, one must know everything or nothing about it." -- Olin Miller
  11. Met her 20 or so years ago - remember it well by Iphtashu+Fitz · · Score: 3, Interesting

    When I was a sophomore in high school our school dedicated its computer lab to her. Her family had a summer place near where I went to school, and she came to the school for the dedication. As one of the geekiest computer people in the school I was chosen as the token pupil to be with her when pictures were taken, etc. I think she was 80 years old when that happened, and she was still sharp as a tack. Her official title at the time was Commodore, and I remember referring to her that way. I also recall her making some comments about programming, etc. that I think helped push me into a career of computer programming before I even realized it. I really wish I had known more about her at the time I met her since I probably would have paid a lot more attention...

  12. She did NOT create COBOL by Tablizer · · Score: 3, Interesting

    COBOL was heavily influenced by Grace's languages, but COBOL itself was designed by a small committee.