Slashdot Mirror


Google Doodle Remembers Computing Pioneer Grace Hopper

SternisheFan writes "Monday's Google Doodle honors computing genius Grace Hopper (remembered as a great pioneer in computing, as well as in women's achievements in science and engineering), on what would have been her 107th birthday, doodling her right where she spent much of her time – at the helm of one of the world's first computers."

157 comments

  1. Grace Hopper Park by Austrian+Anarchy · · Score: 3, Interesting

    I always liked seeing the sign for Grace Hopper Park in Arlington, VA, in front of the apartment complex where she lived for years. Sadly, they did not put "Admiral" on the sign.

    --
    Time Bomber the Book coming soon.
    1. Re:Grace Hopper Park by Anonymous Coward · · Score: 1

      Her Commodore/Admiral rank was only honorary.

    2. Re:Grace Hopper Park by Austrian+Anarchy · · Score: 4, Informative

      Her Commodore/Admiral rank was only honorary.

      No, it was not merely honorary. However, 40 of her degrees were (see same link).

      --
      Time Bomber the Book coming soon.
    3. Re:Grace Hopper Park by Hognoxious · · Score: 1

      I always liked seeing the sign for Grace Hopper Park in Arlington, VA, in front of the apartment complex where she lived for years. Sadly, they did not put "Admiral" on the sign.

      There wasn't room due to all the THIS DIVISION and THAT DIVISION and 77 REDEFINES 01-WS-MY-BUTT stuff which, as far as I'm aware, does absolutely bugger all.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    4. Re:Grace Hopper Park by Virtucon · · Score: 2

      Uh, no it wasn't. Because of her rank there was actually problems promoting fleet operations people to Admiral positions. There's only so many "Admiral Chairs" and she occupied one and she wasn't in fleet operations.. This was one of the main reasons that she was retired by the Navy which she understood when she received the Rear Admiral rank in 1985 and she subsequently retired in 1986.

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
  2. Anybody who doesn't know ... by Anonymous Coward · · Score: 1

    Anybody on Slashdot who doesn't know who she is ... get the fuck out, because you're on the wrong website.

    1. Re:Anybody who doesn't know ... by MyLongNickName · · Score: 5, Insightful

      Anybody on Slashdot who doesn't know who she is ... get the fuck out, because you're on the wrong website.

      You might try wrapping your head around this: obligatory XKCD.

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    2. Re:Anybody who doesn't know ... by Anonymous Coward · · Score: 0

      My kingdom for mod points.

    3. Re:Anybody who doesn't know ... by Anonymous Coward · · Score: 4, Insightful

      Anybody on Slashdot who doesn't know who she is ... get the fuck out, because you're on the wrong website.

      No shame in being a newbie as long as one is *trying* to be a self teacher and tries to not be a newbie forever. In this case, the shame is on the one trying to run newbies off.. You are going to die a lonely death.

    4. Re:Anybody who doesn't know ... by coolsnowmen · · Score: 1

      My kingdom for mod points.

      DEAL!
          Please send the deed for "Anonymous Coward's Kingdom" by way of African Swallow to neverland.
      No takesies-backsies
         

    5. Re:Anybody who doesn't know ... by Anonymous Coward · · Score: 0

      Oh wow... you're going to take responsibility for stuff being posted as Anonymous Coward? My condolences.

    6. Re:Anybody who doesn't know ... by Anonymous Coward · · Score: 0

      On a similar note, this article on the same lines of getting people to actually stop pretending they know and admit that they don't, isn't a bad thing.

    7. Re:Anybody who doesn't know ... by NikeHerc · · Score: 1

      obligatory XKCD

      Interesting timing of this posting. Last night I told two millennials in my wife's family that "Scotty" (James Doohan) lost a finger to a bullet just after D-Day (URL:http://en.wikipedia.org/wiki/James_Doohan). I thought everyone knew this, but neither of them had heard this tidbit before.

      --
      Circle the wagons and fire inward. Entropy increases without bounds.
    8. Re:Anybody who doesn't know ... by Hognoxious · · Score: 1

      Once you know, you're always looking for it. He tended to keep it out of the way.

      Modesty, apparently: he didn't want to be thought of as thinking he was a hero.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    9. Re:Anybody who doesn't know ... by swillden · · Score: 1

      You're a fuckwit.

      Irony so thick you can cut it with a knife.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    10. Re:Anybody who doesn't know ... by SuricouRaven · · Score: 1

      That's now how irony works.

  3. Upon her shoulders*... by Anonymous Coward · · Score: 1

    is much of the modern computing world.

    Without her Jobs, Gates, Zuckerberg, Bezos, etc. would not be where they are today.

    * this is in no way to diminish the other pioneers in the field - Touring, von Newman, von Lovelace, etc...

    1. Re:Upon her shoulders*... by ackthpt · · Score: 1

      is much of the modern computing world.

      Without her Jobs, Gates, Zuckerberg, Bezos, etc. would not be where they are today.

      * this is in no way to diminish the other pioneers in the field - Touring, von Newman, von Lovelace, etc...

      We stand upon the shoulders of giants - paraphrased from Bernard of Chartres

      --

      A feeling of having made the same mistake before: Deja Foobar
    2. Re:Upon her shoulders*... by sconeu · · Score: 5, Funny

      I suspect Jobs *would* be where he is today, since she wasn't researching cures for pancreatic cancer.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    3. Re:Upon her shoulders*... by dubner · · Score: 2

      Without her Jobs, Gates, Zuckerberg, Bezos, etc. would not be where they are today.

      You mean Jobs would be still be alive and Bezos would have hair?

      A pox on you, Admiral Hopper!

    4. Re:Upon her shoulders*... by Hognoxious · · Score: 1

      * this is in no way to diminish the other pioneers in the field - Touring, von Newman, von Lovelace, etc...

      The fact that you didn't manage to spell any of them right diminishes something.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    5. Re:Upon her shoulders*... by RabidReindeer · · Score: 1

      I suspect Jobs *would* be where he is today, since she wasn't researching cures for pancreatic cancer.

      Wouldn't matter, if it's true that Jobs had the treatable kind, since he ignored that route and went all New Age on it instead. Might as well have just loaded up on Laetrile.

    6. Re:Upon her shoulders*... by Anonymous Coward · · Score: 0

      I suspect Jobs *would* be where he is today, since she wasn't researching cures for pancreatic cancer.

      Well if her didn't wast his time with all that computer-junk maybe he would have reaserched cancer treatments.

    7. Re:Upon her shoulders*... by rossdee · · Score: 1

      "We stand upon the shoulders of giants - paraphrased from Bernard of Chartres"

      I thought it was Sir Isaac Newton that said that

    8. Re:Upon her shoulders*... by the_other_chewey · · Score: 2

      this is in no way to diminish the other pioneers in the field - Touring, von Newman, von Lovelace, etc...

      Not to forget Tsu Se, Arbol de Trigo, and l'Oison.

      [hint: Turing, von Neumann, Lovelace-without-von (although an optional "of")]

  4. COBOL by invid · · Score: 1, Interesting

    I think we can blame all the faults of COBOL on the fact that she wanted it to be human readable by business managers. What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

    --
    The Moore-Murphy Law: The number of things that will go wrong will double every 2 years.
    1. Re:COBOL by Anonymous Coward · · Score: 5, Insightful

      I knew somebody would bring that up. In defense of COBOL, 1. Look when it was invented. 2. Look how much staying power it has. 3. Look at the train wrecks caused by later efforts to make easier, more readable programming languages.

      COBOL looks pretty good when you consider all that.

    2. Re:COBOL by ackthpt · · Score: 1

      I think we can blame all the faults of COBOL on the fact that she wanted it to be human readable by business managers. What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      Let us not even broach the sins of PL/1

      --

      A feeling of having made the same mistake before: Deja Foobar
    3. Re:COBOL by dthanna · · Score: 4, Insightful

      At the time you had... Fortran... and Assembler. COBOL was a godsend to the business community. Because of it companies actually invested in computer equipment to do things... that investment reduced the cost and increased its capabilities. Eventually allowing the creation of that smart phone in your pocket. If it wasn't for COBOL it is doubtful that companies would have made the investments.

      Having programed in both COBOL and Fortran... I'll take COBOL for anything business related.

      Yes, it's verbose. But, it was a product of it's time. And quite the amazing language if you know what you are doing with it.

    4. Re:COBOL by SirLurksAlot · · Score: 1

      What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      Ruby and Cucumber (at least for your test code)?

      --
      God, schmod. I want my monkey man!
    5. Re:COBOL by Anonymous Coward · · Score: 5, Insightful

      I think we can blame all the faults of COBOL on the fact that she wanted it to be human readable by business managers. What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      Thank you for that.

      You see, Ms. Hopper, being ahead of her time in MANY respects, knew that programming should be easily done in a human readable fashion.

      Programming computers should be easy. Having difficult to learn languages defeats the purpose of these machines. Being able to program these things should be easy to everyone and the fact that it STILL isn't shows the ineptitude of the computer science world - or arrogance (dude, computers SHOULD be hard to program because it's for smart people or some such nonsense).

      Computers are a tool, The fact that computer languages haven't evolved much since the 1960s is pretty sad.

      ..

      Please oh please post a flame that languages have evolved so that I can spank you hardily - 50 years and we're still typing esoteric computer code?! Seriously?

      If you think that is the way it is, then YOU have NO imagination.

    6. Re:COBOL by ackthpt · · Score: 4, Insightful

      At the time you had... Fortran... and Assembler. COBOL was a godsend to the business community. Because of it companies actually invested in computer equipment to do things... that investment reduced the cost and increased its capabilities. Eventually allowing the creation of that smart phone in your pocket. If it wasn't for COBOL it is doubtful that companies would have made the investments.

      Having programed in both COBOL and Fortran... I'll take COBOL for anything business related.

      Yes, it's verbose. But, it was a product of it's time. And quite the amazing language if you know what you are doing with it.

      Anyone who has actually been suffered to write business applications in FORTRAN IV* would rather be disemboweled by a pack of rabid were-weasels than have to do that again and COBOL would appear to be a gift from Heaven.

      I began my education with, what I considered being taught a load of dead or dying languages, while Object Oriented languages were just on the horizon and Pascal and c were gaining degrees of acceptance. c is still around, but I haven't heard from Pascal in ages - it was fiddly, like Modula2 and seemed to embrace the wordiness of COBOL over the conciseness of c. I've converted systems written in COBOL and at least they were readable - what the coder was doing. FORTRAN business apps are nearly unintelligible.

      * note: use of all caps

      --

      A feeling of having made the same mistake before: Deja Foobar
    7. Re:COBOL by ackthpt · · Score: 1

      What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      Ruby and Cucumber (at least for your test code)?

      How about something from at least the 1960's or 70's? I can still hear those card punching machines - tick-tick-tack-tick-tick...

      --

      A feeling of having made the same mistake before: Deja Foobar
    8. Re:COBOL by Anonymous Coward · · Score: 0

      Sigh. "Assembler" is a tool, not a language.

    9. Re:COBOL by mwvdlee · · Score: 1

      PL/I pioneered the free-form syntax used by C, C++, PHP, Java, C# and most other modern languages.
      What other sins has it committed?

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    10. Re:COBOL by Anonymous Coward · · Score: 2, Insightful

      Agreed, I'm a non techie, and todays computers are less fun and useful than in the win95 era, when I could actually do things with them. Heck, the C64 held far more interest for the average person, you could at least easily learn how to program in basic.

    11. Re:COBOL by Anonymous Coward · · Score: 0

      No. The only fault here is that you are too fucking stupid to understand why that is a "Good Thing (tm)".

      You utter fucking moron.

    12. Re:COBOL by bobbied · · Score: 3

      What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      Lots of comments, very little actual code.

      When I was in school, we had to have over 50% comments or the TA wouldn't even try to grade your program. The habit was a good one, and although I don't always get to the 50% I still put a lot of comments in my code.

      Come to think of it, making your code understandable by the PHB is not a bad goal. If the PHB can understand what you are doing, the next poor programmer (which might be you a few months after you have forgotten the project) will have an easier job fixing something.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    13. Re:COBOL by jfdavis668 · · Score: 1

      PL/I was the first programming language I actually learned, as opposed to picking up as I went.

    14. Re:COBOL by ackthpt · · Score: 1

      PL/I pioneered the free-form syntax used by C, C++, PHP, Java, C# and most other modern languages.
      What other sins has it committed?

      PL/1 incorporated all manner of ugly ways of doing things, borrowing some I/O from COBOL or having something else hacked into it. Inexplicably I had to go back to using PL/1 on one system implementation because the I/O library could hack large I/O buffers, where most other compiler libraries were incapable and was reminded what a sloppy mess of a language it was. You could do just about anything, but it didn't do much of it elegantly. Unless you documented heavily it was difficult to come back to and figure why you did something a particular way.

      One fellow I knew who worked at IBM shunned it for most of the same reasons, it was a quick and dirty language, which was a dumping ground of interfaces.

      --

      A feeling of having made the same mistake before: Deja Foobar
    15. Re:COBOL by leadfoot · · Score: 1

      I have to agree with this one.

      --
      "We're gonna need a bigger boat"
    16. Re:COBOL by Deadstick · · Score: 1

      The WTF blog once featured a tale of woe by a contributor about his interview with a headhunter:

      -Why do you want to change jobs?
      -My employer wants me to become a COBOL programmer.
      -So, you don't like to learn new things?

    17. Re:COBOL by SirGarlon · · Score: 2

      Being able to program these things should be easy to everyone and the fact that it STILL isn't shows the ineptitude of the computer science world

      Programming a computer to do simple things IS easy. You want a program to add up a list of numbers, or compute the value of pi, and I can show you how to do that in a handful of lines of code.

      The trouble is, people want programs that do complicated things like manage a large company's payroll system or model a 3D fantasy world. Even things that sound pretty simple, like managing your calendar appointments, become surprisingly complicated when you try to specify the requirements in detail.

      What I believe is that while there are appropriate tools to for every job, there is no tool or language that makes inherent complexity go away or that makes thorny design problems easy. Neither is there such a thing -- in software or in the physical world -- as a tool that is ultimately powerful and flexible, and requires no skill or knowledge to use.

      I do agree that computers are unnecessarily hard to use, but I disagree with you as to to cause. It's not the language and the process of writing and (usually) compiling code; it's the set of large concepts and abstractions one must master in order to do that effectively, and the mixed success with which OS, language, and application developers communicate those concepts and abstractions to their respective end users.

      --
      [Sir Garlon] is the marvellest knight that is now living, for he destroyeth many good knights, for he goeth invisible.
    18. Re:COBOL by Ultracrepidarian · · Score: 1

      We are assuming that the code actually does what the comment says.

    19. Re: COBOL by Anonymous Coward · · Score: 0, Troll

      COBOL is a sin, it only stayed so long because it's a pain to get rid of it and nobody want to deal with that crap.
      Noone likes COBOL, for an excellent reason : it sucks by design.

    20. Re:COBOL by bobbied · · Score: 1

      True, but I would assume that's a given in most cases.. Not all, just most..

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    21. Re:COBOL by Anonymous Coward · · Score: 0

      I totally get where you are coming from. Fuck I'm old!

    22. Re:COBOL by dthanna · · Score: 2

      You, sir, are confused as you know not of what you speak.

      There is 'The Assembler', and 'Assembler'. The 'The' (definite article) in 'The Assembler' is the thing (program) that assembles Assembler (language) into object code. That is then merged with the linker to a run-time to become an executable. Modern Assembler languages, and by extension 'Their Assemblers', contain macro capabilities - very similar in nature to #include in C (and other such languages). But, back in the 50's, when COBOL was written, not much macro assembler being written.

      Assembler is a language. It has a grammar and a syntax - unless you wish to program in object or straight machine code.

      But don't believe me (I wouldn't) - look for yourself - http://en.wikipedia.org/wiki/Assembly_language

    23. Re:COBOL by bws111 · · Score: 2

      Sigh yourself. The 'assembler' tool does not magically read your mind and spit out code. You must actually provide input to the assembler. And this input is in, wait for it, Assembler Language! Shocking, I know!

    24. Re:COBOL by dthanna · · Score: 1

      There are a few that are better than their predecessors....I'll posit SAS and Mathmatica / Wolfram as examples. Mathmatica on my R-Pi - yum.. a bit slow, but still great (Thanks Stephen!).

      But, I would agree, that in general we have peaked at C and complexity has abounded due to K&R's 'I hate to type' mantra. Just about every popular language in the last 30 years has been 'C-like' - C, C++, C#, Java, Python, JavaScript, etc. Some are better than others, but all have a coding style that can be overly dense.

    25. Re:COBOL by slapout · · Score: 0

      I agree that we should try to make things simple. But I also think that COBOL's verbosity gets in the way of that. For example, I find:

      For i = 1 to 100
          ' Do work here
      Next

      to be simpler and easier to understand than

      PERFORM VARYING WS-I FROM 1 BY 1 UNTIL WS-I = 100
      * DO WORK HERE
      END PERFORM

      --
      Coder's Stone: The programming language quick ref for iPad
    26. Re:COBOL by camperdave · · Score: 1

      ...human readable by business managers...

      Ah!!! That explains a lot.

      Um... except why anything needed by business managers needed to be HUMAN readable.

      --
      When our name is on the back of your car, we're behind you all the way!
    27. Re:COBOL by RabidReindeer · · Score: 1

      True, but I would assume that's a given in most cases.. Not all, just most..

      I take it you don't work in the business, then.

      I think one of the "Murphy" laws covers what happens to code once you document it.

    28. Re:COBOL by invid · · Score: 1

      Here I am pointing out that what many people consider to be a problem with COBOL, that it is too wordy, has in fact a functional purpose. Although, using the word PLUS for '+' did go a bit too far. I have to assume most business managers know what '+' means.

      --
      The Moore-Murphy Law: The number of things that will go wrong will double every 2 years.
    29. Re:COBOL by mythosaz · · Score: 1

      I've always found COBOL quite readable. Math, especially, always looked clean.

      SUBTRACT 10 FROM WS-A GIVING WS-B

      DIVIDE WS-A INTO WS-B GIVING WS-C REMAINEDER WS-D

      And I think this stolen example of conditional code is also pretty clear to read...

        IF WS-AMT IS NUMERIC
                          ADD WS-AMT TO WS-BANLANCE
                  ELSE
                          MOVE ZEROS TO WS-AMT
                          PERFORM ERROR-PARA.
                  END-IF.

      [COBOL is incompatible with the lameness filter...]

    30. Re:COBOL by RabidReindeer · · Score: 1

      Computers are hard to program because computers are stupid. That's why the most deadly words ever spoken in the industry are "All You Have To Do Is..." It's hard enough to get other humans to do things right when you tell them what to do, much less computers.

      Some programming languages look more or less like English such as COBOL. Some look more or less like mathematical notation, such as FORTRAN or APL. Some are basically mathematical/symbolic notations on drugs. Each has its advantages, but none of them - including English-like languages such as COBOL - actually have succeeded in the Holy Grail of allowing the production of properly-functioning software by underpaid chimpanzees in a handful of hours, much less in a way that can actually be read and understood. And maintained.

      COBOL is especially evil because the PHB's think that they understand the program simply because it's in "English". In reality, their beady little eyes glaze over and they quickly push it aside because their time is too valuable to go through all that crap. Which is how the sins of the programmers avoid discovery.

    31. Re:COBOL by JaredOfEuropa · · Score: 1

      They had better PHBs back then. No, seriously.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    32. Re:COBOL by bws111 · · Score: 1

      To a non-programmer, what exactly about that 'for' statement implies 'loop'? It could just as easily mean 'if i is between 1 and 100 do work here'. On the other hand, the COBOL example seems pretty unambiguous.

    33. Re: COBOL by Anonymous Coward · · Score: 1

      Noone would appreciate it if you don't tell other people what he does or doesn't like.

    34. Re:COBOL by slapout · · Score: 1

      Try writing the COBOL version over and over everyday and you'll get tired of it pretty quickly.

      --
      Coder's Stone: The programming language quick ref for iPad
    35. Re:COBOL by Anonymous Coward · · Score: 0

      PL/I differed from C in that C didn't have a lot of hacked in stuff. The two languages are alike in that they let you do lots of things, even write entire, sophisticated operating systems. Multics was written in PL/I and it was an early example of a multi-user, multi-tasking, multi-CPU, shared memory system with strong security.
      Another way they are similar is that both will let you easily write code that will crazy things and be very difficult to debug.

    36. Re:COBOL by invid · · Score: 1

      Correction, I meant 'ADD', not 'PLUS'. It's been over 20 years since I've programmed in COBOL and I've done my best to block it out of my mind.

      --
      The Moore-Murphy Law: The number of things that will go wrong will double every 2 years.
    37. Re:COBOL by bws111 · · Score: 2

      Nobody ever claimed COBOL was intended to make life easy for developers. COBOL was designed so the people who actually bear responsibility for the business (and who are certainly not the developers) can verify that their business processes are implemented to their liking. These people include not only bosses, but also financial people, lawyers, auditors, etc.

    38. Re:COBOL by bobbied · · Score: 1

      I was commenting on MY comments and those of whom I work with. In general, our comments are related to the code they document, by design, by policy and by routinely checking them in code reviews. Do they always match 100%? No, but that is the exception and not the rule, at least where I work. I fully get that my current experience is *NOT* the norm. Out of the 9 places I've worked as a programmer, my current employer is certainly at the top of the list for producing quality code. Only a few have rivaled the place I work now. The rest where usually pretty bad.

      Of course, if you work in a place that doesn't care, you get what you get. Stupid programmers, or programmers who are being driven too hard to care, will not review comments and code for readability and make sure the two match. But it's a short term gain and a long term loss when you don't put the effort into producing code that is maintainable. These programmers are the same types that choose misleading identifier names and produce methods with huge complexity. They don't understand the difference between the stack and the heap or exactly what their code actually does, as long as the compiler will plow though it and the program runs.

      So your mileage may vary from mine... Especially if you work in one of the majority of places that really don't know what they are doing.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    39. Re:COBOL by Anonymous Coward · · Score: 0

      Mod parent up, everyone who has a bank account uses COBOL programs daily, most just don't know about it.

    40. Re:COBOL by Krishnoid · · Score: 1

      What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      What would it look like? Each line must have a key in the first column:

      • Increases profits
      • Cuts costs
      • The competition is doing it
      • Helps us meet our ship date
      • Makes you look good to the VP

      or it will fail to compile.

      v.2 will have the compiler generate a histogram of keys for a given source file, and the make tool would actually generate graphs. I'm sure a real programming language designer can improve on the design.

    41. Re:COBOL by slapout · · Score: 1

      That's just it though -- business people don't read code! You're making the developers lives harder in order to cater to a situation that never happens.

      --
      Coder's Stone: The programming language quick ref for iPad
    42. Re:COBOL by swillden · · Score: 1

      Anyone who has actually been suffered to write business applications in FORTRAN IV* would rather be disemboweled by a pack of rabid were-weasels than have to do that again and COBOL would appear to be a gift from Heaven.

      Ah, but a Real FORTRAN programmer can write FORTRAN in any language. You ain't see nothing until you've seen a payroll system written in FORTRAN... using COBOL.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    43. Re:COBOL by swillden · · Score: 1

      Hmm. I always thought assembly language was the input and the assembler was the tool. However, I turned to Wikipedia for support and found that usage is inconsistent.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    44. Re:COBOL by swillden · · Score: 1

      What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

      Lots of comments, very little actual code.

      When I was in school, we had to have over 50% comments or the TA wouldn't even try to grade your program. The habit was a good one, and although I don't always get to the 50% I still put a lot of comments in my code.

      That's a very bad habit, and one that you should break. Comments are evil. They are occasionally -- very occasionally -- a necessary evil, but still evil. I'll explain below.

      Come to think of it, making your code understandable by the PHB is not a bad goal. If the PHB can understand what you are doing, the next poor programmer (which might be you a few months after you have forgotten the project) will have an easier job fixing something.

      Absolutely, you want your code to be extremely easy to understand. In fact, that's the #1 goal, even ahead of doing the correct thing, because bugs are more likely to get fixed than unreadability, and in the long run they cost less. Comments are one way of achieving readability, but they're a crutch. Worse, they're a crutch with a built-in time bomb.

      The problem with comments is that they're wrong, and they mislead the next poor programmer.

      They're usually approximately correct (though rarely exactly correct) when written, but they tend inevitably towards inaccuracy as time goes on, because the code will eventually get changed, while the comments may or may not get updated to stay current. If maintainers assiduously update the relevant comments every time they change the code, then the comments stay (approximately) correct, but at the expense of requiring that additional effort by the maintainers. If someone doesn't bother to update the comments, it gets bad.

      On the other hand, code that is readable without comments doesn't increase the maintenance burden and has the fantastically valuable characteristic of always being correct. Comments can be wrong about what the code does, but the code is never wrong. It may not do what is desired, but what it says is what it does (barring compiler and hardware bugs, but that's a separate problem).

      I should clarify here that I'm talking about comments intended for maintainers. I have no issue with Doxygen/Javadoc/etc. comments that are used to generate documentation. They're just as error-prone, but they provide enough additional value -- in the form of the generated documentation -- that they're worth the risk and the cost. They're written, not for future readers of the code, but for future programmers who may be able to avoid reading the code.

      Comments that are written for future readers of the code, however, are a code smell. They're not absolutely bad, but any time I see a comment embedded in code, it's an indicator that there's a good chance the author should have put some more time in, finding ways to make the code readable without the comment. Actually, I tend to write lots and lots of comments in my code while I'm building it, outlining the functionality I'm going to write before I write it, explaining why it's there and what it's goal is. But as I implement it, I read each section of code to decide if it's sufficiently clear that I can remove the comment. If not, I refactor until it is. In very rare cases I find that there is simply no way to make it clear without a comment, generally because there are very subtle constraints on the code which cannot be expressed in the code. Those cases are rare.

      Often it's just a matter of taking a block of code with an explanatory comment at the top and factoring it out into a subroutine, with a well-chosen name that expresses what the comment used to say. If you find there's no such name that isn't a dozen words long, you need to go farther and restructure. In many cases you can eliminate comments just by adding some variables in which to place intermediate res

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    45. Re: COBOL by gmhowell · · Score: 1

      Noone would appreciate it if you don't tell other people what he does or doesn't like.

      FTFY, kid.

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
    46. Re:COBOL by Bongo · · Score: 1

      "Having a conversation with the sketchbook" is a notion in visual design like architecture or construction. For little scripting tasks, I find talking to the comments an exercise in clarifying what I am trying to do and why. The intention, the way it fits the bigger picture. The code is the reality, the comments are the mental intention. Unless it is a very well understood area where to be a programmer you really have to know the domain and the problems very well, so the code is immediately obvious to the trained eye. But for run of the mill make stuff up as we go along problems, the intention needs to be talked about, methinks.

    47. Re:COBOL by Bongo · · Score: 1

      I don't disagree but I'm reading someone's code at the moment, some routines in R, and the word "training" is in the name of a routine, but it doesn't explain in which sense of the word "training". So now I have to try to figure out the meaning of the result. I'm sure it was obvious to the author. Maybe fine grained comments are bad, but an overall story explaining in ordinary words the overall intent and picture would be nice. Anyway, IANAP.

    48. Re:COBOL by swillden · · Score: 1

      Yes, an overarching narrative is very important. If you're using something like Javadoc or Doxygen, the documentation comments are a fair place for it, but what's often even better is to put it in a design doc, which should be linked from or stored with the code. Design documents also get outdated and become wrong if not maintained, but they should be at a sufficiently high level that this happens very slowly.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    49. Re:COBOL by sensei+moreh · · Score: 1

      PL/1 was the language taught in the only programming class I ever took. I wonder if I still have the textbooks for that class buried somewhere in the basement.

      --
      Geology - it's not rocket science; it's rock science
    50. Re:COBOL by bobbied · · Score: 1

      Most of my comments are Doxygen, at least from a line count perspective. I try to document every method's inputs, returns and what it reads and modifies and what it is attempting to do. In addition to that, I try to clearly document any identifiers declared, their content and purpose. Finally, I attempt to document every logical edge and loop control logic. Adding all this gets you pretty close to half your source code being comments.

      I actually do most of the commenting BEFORE writing the code in question. We usually do not have highly detailed design documentation beyond the class public methods so this is my way of fleshing out the implementation details before I code. Your mileage and practice may vary, but any process that discourages the production and maintenance of comments is stupid in my book. Sure, you have to *maintain* comments along with the code, but the time you save when you have to pick up some code to maintain it later is going to make it worth it in most cases. Of course, if you don't intend to maintain your code (and the comments in it) then feel free to ignore good programming practice but be aware that you will pay the price for this, eventually.

      So, I don't agree that "comments bad" they are not. In my experience, they are not used enough.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    51. Re:COBOL by Anonymous Coward · · Score: 0

      Making something that everyone can do easily generally ends with making something that is incapable of doing anything useful, apart from maybe one very inflexible function. If you think otherwise, you haven't been paying attention.

    52. Re:COBOL by Anonymous Coward · · Score: 0

      I took a grad school AI class, using both Prolog and Lisp. One of my colleagues only had a FORTRAN background.

      I must say I was astounded at how well he was able to write FORTRAN code using Lisp... I would have said it was impossible, but he did it. It was a good lesson to me, too, in the concept of hammer..nail.

    53. Re:COBOL by Anonymous Coward · · Score: 0

      I should clarify here that I'm talking about comments intended for maintainers. I have no issue with Doxygen/Javadoc/etc. comments that are used to generate documentation. They're just as error-prone, but they provide enough additional value -- in the form of the generated documentation -- that they're worth the risk and the cost. They're written, not for future readers of the code, but for future programmers who may be able to avoid reading the code.

      Often it's just a matter of taking a block of code with an explanatory comment at the top and factoring it out into a subroutine, with a well-chosen name that expresses what the comment used to say. If you find there's no such name that isn't a dozen words long, you need to go farther and restructure. In many cases you can eliminate comments just by adding some variables in which to place intermediate results of a calculation -- variables with well-chosen names that express what the business meaning of that intermediate result is, generally including its units, except where they're obvious (which is less often than you might think). Function/method names, variable names, class names, etc. are how you can make the meaning and purpose of your code clear without requiring comments

      So instead of having a block of code with an explanatory comment at the top which can not possibly serve a generic purpose, you want people to refactor it into one or more functions, each with their own explanatory comment at the top for generating documentation, even though they have hardcoded values inside which prevent their use anywhere other than where the original code was. (Oh, I'm sorry, you were obviously assuming everyone codes according to your pristine standards. I guess you haven't actually worked on code professionally in a while...)

      Sounds like 3x the work for 0.25x the functionality, with an overall increase in entropy.

    54. Re:COBOL by swillden · · Score: 1

      So instead of having a block of code with an explanatory comment at the top which can not possibly serve a generic purpose, you want people to refactor it into one or more functions, each with their own explanatory comment at the top for generating documentation

      No, these subroutines aren't part of the public interface, and not only don't need documentation comments, but shouldn't have them.

      even though they have hardcoded values inside which prevent their use anywhere other than where the original code was

      Uh, that's another problem. You should always at least extract those to constants.

      I guess you haven't actually worked on code professionally in a while

      LOL. Well, I've only written a little code today because most of it has been spent in meetings. Tomorrow will be more productive, though.

      Sounds like 3x the work for 0.25x the functionality, with an overall increase in entropy.

      Nonsense.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    55. Re:COBOL by swillden · · Score: 1

      Most of my comments are Doxygen, at least from a line count perspective. I try to document every method's inputs, returns and what it reads and modifies and what it is attempting to do.

      This part is good. Documenting every identifier is generally not a good idea; instead put the effort into naming identifiers so they're self-documenting. Same with documenting every logical edge; put the effort into making the code itself explain the intent and rationale.

      Sure, you have to *maintain* comments along with the code, but the time you save when you have to pick up some code to maintain it later is going to make it worth it in most cases.

      Only if you ignore the time it will cost you when the comments are wrong, which tends to be orders of magnitude higher.

      So, I don't agree that "comments bad" they are not. In my experience, they are not used enough.

      I used to feel the same way, then I acquired more experience, on larger codebases.

      For a more complete explanation of why comments are bad, I recommend Martin Fowler's book "Refactoring: Improving the Design of Existing Code". There are a few other books that cover it as well, but I think Martin's chapter on the topic explains it concisely and effectively.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  5. mixed feelings... by Anonymous Coward · · Score: 0

    she's definitely historically significant but as someone who had the misfortune of running MVS/CICS/VSAM applications for several years I have a hard time celebrating anything associated with COBOL...

  6. If you're not up on your computer history. by wjcofkc · · Score: 2
    --
    Brought to you by Carl's Junior.
  7. Women in IT by slapout · · Score: 3, Funny

    You know why there aren't a lot of women in IT now, right? It's because after Grace Hopper unleashed COBOL, we're been leery about letting them in.

    (It's a joke! Claim down.)

    --
    Coder's Stone: The programming language quick ref for iPad
    1. Re:Women in IT by TechyImmigrant · · Score: 1

      >(It's a joke! Claim down.)

      I claim up. It's higher.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  8. many early programmers were female by peter303 · · Score: 0

    Before the late 1940s the word "computer" refered to clerks who computed mathematical tables (e.g. weapon trajectories) by hand or mechanical calculator. All these clerks were female and their bosses males. So when the first anlog and digital computers came along in the late 1940s, some of their clerks became their programmers. Programming was by rewiring switchboards or punch tape in those days. The electrical engineers and mathmaticians who built the hardware were mostly male. Soem of them migrated into software too.

    1. Re:many early programmers were female by Anonymous Coward · · Score: 0

      Programming was by rewiring switchboards or punch tape in those days. ...The electrical engineers and mathmaticians who built the hardware were mostly male.

      And those males would refer to those able, competent women as "Rosies" (taken from "Rosie the Riveter"). Once WWII was over men returned to the job market, and those women mostly got displaced.

    2. Re:many early programmers were female by SirGarlon · · Score: 2

      There is a documentary about this, which I saw on Netflix (I don't remember if it was streaming or DVD) called "Top Secret Rosies." I knew about that history from my physics and math background, but my wife was amazed to hear it. Anyway, the film is worth watching.

      --
      [Sir Garlon] is the marvellest knight that is now living, for he destroyeth many good knights, for he goeth invisible.
    3. Re:many early programmers were female by barlevg · · Score: 1

      More on this, I was taught that a lot of the principles behind MPI and other distributed memory parallel programming come from how calculation work was distributed among the women "computers" working at Los Alamos during the time of the Manhattan project.

    4. Re:many early programmers were female by alexander_686 · · Score: 1

      Not really. Both before and after WWII “computers” was a female dominated field, like nurses or teachers.

      After WWII, well, I am not sure displaced is the right word. We are talking about a rapidly evolving field. Most of the jobs that men took in the computer field just did not exist at the start of the war. Virgin ground so to say. Not so much as displacing but rather being left behind.

    5. Re:many early programmers were female by Deadstick · · Score: 1

      I had the pleasure of speaking with one of the Rosies some years back. I was trying to line her up as a speaker at my workplace's "Women's Issues" month, but she lived too far away and the company wouldn't buy the plane ticket.

      They have an association, naturally...they call their daughters Rosettes and their sons Rivets.

  9. Re:Whatever by Anonymous Coward · · Score: 0

    Exactly my thoughts as well.

    Idiot white men.

  10. Re:Thanks, but by ArcadeMan · · Score: 2, Interesting

    Really? I never see the Google "home page" anymore, I just type something into the address bar, if it's not a URL then it sends it as a search to Google and gives me the results

    Yes, the Google logo on the left is a bit different than usual but not enough to tell me what it was about.

  11. Who cares! by Anonymous Coward · · Score: 0

    The doodle is a topic of interest? You've got to be kidding me.

  12. Forgiveness by SonnyDog09 · · Score: 2

    One of my favorite quotes is from her: "It is far easier to ask for forgiveness than permission."

    --
    Your "fair share" is NOT in my wallet.
    1. Re:Forgiveness by Anonymous Coward · · Score: 0

      That's an old, popular U.S. Military "proverb" that pre-dates even her.

    2. Re:Forgiveness by QilessQi · · Score: 1

      FWIW, the Daily Mirror* does attribute the quote to her. Not sure where they got that from:

      http://www.mirror.co.uk/news/technology-science/technology/grace-hopper-top-10-facts-2907958

      * Yeah, yeah, I know.

  13. Google Google Google by Anonymous Coward · · Score: 0

    Bing is doing the same thing but no mention of them.
     
    I guess that's what you get when there's nothing here but a bunch of Fandroids.
     
    A much more interesting article is about how Google wants to ban civilians (ie Amazon) from building a drone delivery system. So Google is going to bend the ear of the legislature to try to get an unfair edge against a competitor. Why isn't that being reported on? Why not headlines about the evil inherent in Google?

    1. Re:Google Google Google by barlevg · · Score: 1

      Hmmm... when I go to bing.com today I see an 1800s difference engine. No mention of Admiral Hopper.

      Ooh! I found it! If you mouse over the difference engine, there's a box on the left that, when you mouse over it, says that today is the birthday of... shoot--I have to click the link.

    2. Re:Google Google Google by Anonymous Coward · · Score: 0

      Your point being?
       
      You're just another goosestepping Fandroid.

    3. Re:Google Google Google by barlevg · · Score: 1

      My point was that Bing was *not* doing the same thing, as the AC was claiming. Mentioning her in an obscurely hidden side-link is very different than featuring her prominently where everyone will see.

  14. Re:Whatever by Deadstick · · Score: 2

    Well, see, the first woman to publish in mathematics was stripped naked and dragged to death behind a wagon, and it's been an uphill swim ever since...

  15. Oblig. SMBC by barlevg · · Score: 4, Funny
    1. Re:Oblig. SMBC by Josh-Levin · · Score: 1

      I understand that she handed out "light-nanoseconds", copper wires 11.8" long. Actually, 11.8" is how fast light travels in a vacuum. Electrical signals travel slower than that in copper, a little bit slower in unshielded wire, and 2/3c in coaxial cable (see http://en.wikipedia.org/wiki/Speed_of_electricity)

  16. Re:Thanks, but by barlevg · · Score: 2

    My version of Chrome now shows the doodle on the "New Tab" page. I'm glad. I always hated missing them.

  17. met her 30 years ago. by Anonymous Coward · · Score: 2, Interesting

    I got to MEET her. I was a faculty brat at Syracuse where she was a graduation speaker, and through a lot of begging, my dad got me a seat at the speakers table, and she held forth, drinking straight scotch, smoking unfiltered Pall Malls and swearing for two hours. One of the best moments in my life. I'll never forget it, and she's been an inspiration through my career.

    And I have a nanosecond.

    1. Re:met her 30 years ago. by Entropius · · Score: 1

      So she was a sailor, then? :)

    2. Re:met her 30 years ago. by amicusNYCL · · Score: 1
      --
      "Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
    3. Re:met her 30 years ago. by Anonymous Coward · · Score: 0

      Wow, hey, lucky you. That must have been something. Odd, isn't it, how some of the greater treasures are among the more fleeting.

      "Why does it take so long to talk to a satellite?" Yeah. Great memento, that nanosecond.

  18. Re:Whatever by Anonymous Coward · · Score: 0

    Hypatia?

  19. Google Doodle - the same stuff by Anonymous Coward · · Score: 0

    every year - SSDD ad infinitum

  20. How long is a nanosecond by aslvstr · · Score: 1

    I attended a talk she gave in the early 80's. She was quite an entertaining speaker. She was able to describe some concepts in an easy way to undersand way. Like how long is a millisecond or a nanosecond? She handed out nanoseconds at the end. I still have that little 11.8 inch piece of wire.

    1. Re:How long is a nanosecond by Ultracrepidarian · · Score: 1

      Yes, one light foot.

    2. Re:How long is a nanosecond by NikeHerc · · Score: 1

      She handed out nanoseconds at the end.

      I was fortunate to hear her speak on two occasions in the 70s. Packed up with all my XDS/SDS stuff is a pair of Grace's nanoseconds.

      --
      Circle the wagons and fire inward. Entropy increases without bounds.
  21. Fond memories of a grand lady... by whizbang77045 · · Score: 2

    I have fond memories of her. On the one occasion I got to see her in person, I was a member of a student ACM chapter, and she was our guest speaker. I remember that she had very strong opinions, particularly about IBM.

    At the time, the System 360 was all the rage, and had blue cabinets. She brought an 8080 to the presentation in a small, blue plastic case, commenting that she'd heard computers came in blue boxes. She also commented (again about the 360) that it couldn't be much of a machine, since it spent half of its time talking to itself, a reference to the operating system overhead.

    I've often wondered what she'd think of computers and operating systems today, particularly Windows and Linux.

    R.I.P. Grace Hopper. You're a hard lady to forget!

    1. Re:Fond memories of a grand lady... by game+kid · · Score: 1

      Hell, I wonder what she'd think about that other 360.

      --
      You can hold down the "B" button for continuous firing.
    2. Re:Fond memories of a grand lady... by SternisheFan · · Score: 3

      Here she is on David Letterman, about 27 years ago... http://www.youtube.com/watch?v=1-vcErOPofQ

  22. Re:Whatever by Deadstick · · Score: 1

    Yes.

  23. Glad to have heard her speak live by dreamweaver7777 · · Score: 1

    I had the honor of hearing her speak as a guest lecturer when I attended Ohio State. I remember her showing us the nanoseconds! An original geek, an outstanding technologist, a wonderful human being. And, oh yes, a woman.

    --
    dreamWeaver
  24. Grace used CamelCase? I think not! by theodp · · Score: 1

    Back in the day, COBOL names were UPPERCASE and used hyphens. So, Grace would have used CURRENT-YEAR, not CurrentYear, as the Google Doodle does. :-)

  25. Congratulations on your 7th birthday! by PPH · · Score: 4, Funny

    Only allowed two digit ages and forgot to handle the overflow flag.

    --
    Have gnu, will travel.
  26. Some fun Grace Hopper info by sl4shd0rk · · Score: 3, Informative

    "If it's good idea, go ahead and do it. It's much easier to apologize than it is to get permission." --Grace Hopper

    * credited with popularizing the term "debugging" for fixing computer glitches

    * Navy destroyer USS Hopper (DDG-70) is named for her, as was the Cray XE6 "Hopper" supercomputer at NERSC.

    * at the age of seven she decided to determine how an alarm clock worked, and dismantled seven...

    * bachelor's degree in mathematics and physics

    * wrote her own compiler in 1952.. "Nobody believed that," she said. "I had a running compiler and nobody would touch it. They told me computers could only do arithmetic."

    More here of course: http://en.wikipedia.org/wiki/Grace_Hopper

    --
    Join the Slashcott! Feb 10 thru Feb 17!
    1. Re:Some fun Grace Hopper info by barlevg · · Score: 1

      * credited with popularizing the term "debugging" for fixing computer glitches

      You left out the story of why it's called debugging! From Wikipedia:

      While she was working on a Mark II Computer at Harvard University, her associates discovered a moth stuck in a relay and thereby impeding operation, whereupon she remarked that they were "debugging" the system.

    2. Re:Some fun Grace Hopper info by TheHawke · · Score: 1

      And beat managers over the head with a cluebat, stating "the most damaging phrase in the English language is `We've always done it this way.'"

      I know of a few dozen or so managers to this day that needs that cluebat applied to...

      And then some.

      --
      First rule of holes; When in one, stop digging.
  27. Re:Whatever by Entropius · · Score: 3, Interesting

    The realm of women is whatever they want it to be. There is substantial cultural inertia, especially in places like the Southeast US, that impedes young women from trying to "do computers and tech stuff", and so the lampshading of legitimate achievements made by folks like Hopper is no bad thing. Yes, were she male she wouldn't get quite as many accolades, but so? She was a pioneer, and there is no shame in pointing out to today's young women "want to become a computer scientist? You're in good company."

    I have as much distaste for postmodern cultural wankery as you, but informing women that they are welcome in the scientific community ain't that.

    I taught computational physics for a couple of years as a grad student. Of the students that I considered absolutely top-notch, about 60% were women (where the difference from 50% is statistical noise). As far as physics went, they were basically the same as the men.

  28. I wondered if this carried an academic stigma by peter303 · · Score: 1

    When I was at MIT in the 1970s there was not an official computer science major yet, even though were several prominant computer science labs that every student wanted to play in. Compuer science was a minor in EE, ME, and business. In 1980 MIT recognized a formal CS degree.
    I wondered if the procrastination was due to the "taint" of programming being a trade-school craft and not a real scientific discipline. And that in turn due to its early female participation.

  29. syntax or logic? by Anonymous Coward · · Score: 0

    my experience has been that PHB's struggle far more with LOGIC (do it this way unless it's the 2nd Tuesday of the month & a full moon business rules) than code itself...

  30. // to do: UML joke goes here by Hognoxious · · Score: 1

    What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

    It'd have a lot more pictures in it.

    Say, isn't it drag/drop/drool/click programming's turn at the top of the hype heap again?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  31. nanosecond by p51d007 · · Score: 0

    I still remember her on Letterman and her giving him one of her nanoseconds :)

  32. Re:Whatever by Hardhead_7 · · Score: 2

    I completely agree, except the part where you said she wouldn't get quite as many accolades. She wrote the first compiler. That's fucking seminal! Who else can claim a first that big?

  33. 107?? by Citizen+of+Earth · · Score: 1

    The COBOL program should be subtracting 06 from 13 giving 7!

  34. Google's first try got the age algorithm wrong (!) by Eternal+Vigilance · · Score: 2

    The first version of this Doodle got the algorithm to compute age wrong (!). The original version of the Doodle used the COBOL expression

    SUBTRACT CurrentYear FROM BirthYear GIVING Age

    which actually computes the negative of the age (for most people born after Christ, anyway).

    I wondered whether this might be a nod to her pioneering work in software debugging, as also referenced in the flying moth at the end of the animation, but since Google has since corrected the bug, it seems even the mighty Google still sometimes commits the simplest of programming errors. (Right on their main page and logo, too. Oooops. I suppose there's also the view that the code was wrong because it was a woman doing the coding. You misogynist Google bastards.)

    Whatever the reason, happy birthday and many thanks to Amazing Grace.

    (full disclosure: I submitted this as a story overnight, but since it didn't get picked up, it seemed too funny to let it completely slip into the ether.)

  35. Anybody who doesn't *bother to* know ... by dlenmn · · Score: 2

    There's nothing wrong with not knowing something important; the sin is not lifting a finger to find the fact out -- e.g. people seemingly incapable of typing a name into wikipedia and reading the first paragraph (and then whining about it in the comments instead in hopes someone will spoon-feed it to them). Those are the people who need to get lost.

    1. Re:Anybody who doesn't *bother to* know ... by bickerdyke · · Score: 1

      Or even easier: Just click on the &/&%" doodle!

      --
      bickerdyke
  36. She was a computer prophet by Anonymous Coward · · Score: 5, Informative
    1986 interview:

    Chips Ahoy: Do you think the current popularity of micros is just a fad?

    Hopper: No, the big mainframes are going to disappear. In fact, I intend to scuttle them. They have to go. They’ll be too slow. We’ll build systems of computers. It will be a whole bunch of micros, and they’ll all call each other up and talk. If you use a big mainframe, first you have to do inventory and then you do payroll and so on. You might just as well have a micro doing each of those jobs all working in parallel. That’s the way you get the speed. The big pressure is going to be on faster answers. There never was a good reason for putting inventory and payroll on the same machine. The only reason you did it was because you could only afford to own one computer. That’s no longer true. The micros are as big [in terms of processing capacity] as mainframes were only 10 or 12 years ago. Back then a big mainframe had 64K. That’s smaller than today’s micros by a long shot.

    Chips Ahoy: Is there a limit of what micros can do for us?

    Hopper: They’ll only be limited if our imaginations are limited. It’s all up to us. Remember, there were people who said the airplane couldn’t fly.

    http://www.history.navy.mil/bios/hopper_grace.htm#limits

    1. Re:She was a computer prophet by John+Allsup · · Score: 1

      Though she missed the issue of reliability.  There's a reason certain mission critical setups don't run simple micros.  And supercomputers that use Xeon and suchlike are more than just micros in how they link things together.  But apart from those situations, yes, she was right: now micros dominate.

      --
      John_Chalisque
    2. Re:She was a computer prophet by Anonymous Coward · · Score: 0, Funny

      What relic of history many slashdotter won't let go of is typing their posts in GODDAMNED COURIER-LIKE FONTS. Get with the times, grandpa. Just because you have a 3 digit UID does not excuse you from keeping up with technology. Or are you seriously typing from a VT100 terminal?

    3. Re:She was a computer prophet by drinkypoo · · Score: 1

      Though she missed the issue of reliability. There's a reason certain mission critical setups don't run simple micros.

      Yes, they run clusters.

      And supercomputers that use Xeon and suchlike are more than just micros in how they link things together

      Yes, they are micros with very fancy network cards.

      But apart from those situations, yes, she was right

      Your ego has run away with you, sort of like your need for antiquated affectations evinced by your need to make people read your comment in monospace. She was right, and you're wrong, and shut up.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:She was a computer prophet by SuricouRaven · · Score: 1

      "Just because you have a 3 digit UID does not excuse"

      A 3-digit UID excuses anything.

    5. Re:She was a computer prophet by Anonymous Coward · · Score: 0

      Except that modern PC servers are no longer "simple micros." They now have redundant, hot-swappable power supplies, main boards, and drive arrays. Micros were better at getting big than dinosaurs were at slimming down. Arguably less elegant than the big iron of old, but just as reliable/maintainable, much more flexible, and (of course) much cheaper.

  37. Logic error in the doodle by BHS_Turf · · Score: 1

    Display output would be -107

  38. Necessary evils. by westlake · · Score: 1

    I think we can blame all the faults of COBOL on the fact that she wanted it to be human readable by business managers. What would your programming language look like if the Pointy-Haired Boss had to be able to understand it?

    How many programmers of that era were expert in modern corporate accounting, law, banking, business practices and procedures, as they had evolved over the past three or four centuries --- and not merely knowledgeable, but credentialed, as a C.P.A., for example?

    In turn, how many accountants could have read and validated FORTRAN code for accounts receivable?

  39. COBOL was an arrow in the pioneer's back by Tablizer · · Score: 4, Insightful

    You may scoff at COBOL, but she pioneered the idea of using a more human-friendly notation instead of machine language and its cousin, assembler. Her experiments were the precursor to Algol, which shaped all the imperative block-oriented languages we use today, including C, Java, VB, Pascal, etc.

    And it made software more vendor-independent as the languages were not tied to a specific machine architecture, unlike machine code and assembler.

    Before that, many scoffed at the idea of "dumbing down" programming with English-like syntax, fearing it would waste resources and invite poorly educated riff-raff into the field. (Well, maybe it did :-)

    Perhaps Grace didn't get it quite right on the first try, but she helped spark a computer language revolution that led to better tools down the road. She tested waters others feared.

  40. Hmm... by Greyfox · · Score: 1

    If I'd invented COBOL during the course of my career, I'd have blamed it on a subcontractor.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  41. Re:Google's first try got the age algorithm wrong by klui · · Score: 1
  42. Critics of COBOL often forget by Anonymous Coward · · Score: 0

    1. The primitive systems it ran on (and ran well on, all things considered)

    2. The early COBOL programmers came to it often w/o experience in other languages (so it worked well enough for beginners and pros)

    3. There are still MANY systems in our economy still running COBOL code for very important tasks (it's held up amazingly well... better than most languages)

    I wrote my share of COBOL code many years ago (wrote lots of FORTRAN too) now it's C,C++,C#, or assembler for me (depending on target and project) but I still maintain a healthy respect for both COBOL and FORTRAN and their developers. Most younger programmers have never experienced punch cards, Teletype terminals, etc and therefore do not fully comprehend either the environment in which these languages arose or the leap forward that they provided... that's not an insult - most car drivers have no experience with buggy whips - but younger users of any tech often cannot grasp the full impact of inventions that pre-date them.

  43. Re:Google's first try got the age algorithm wrong by Eternal+Vigilance · · Score: 1

    Nope, stopped reading reddit long ago after discovering the mods' penchant for silently censoring comments and entire story threads they didn't like.

    That the original Doodle might have accurately depicted poor-but-industry-accepted COBOL coding practices (i.e., approving and committing code where the program logic is wrong but the result of the calculation may still appear correct if an invisible dependency on a separate section of the program happens to work out in the programmer's favor) is either deeply nuanced, deeply disturbing, or both. ;-)

    (Showing enough COBOL to correctly calculate age-in-years would make for a verrrry long Doodle.)

  44. Re:Google's first try got the age algorithm wrong by Anonymous Coward · · Score: 0

    It was an honest mistake (as almighty as it may seem, Google is run by people, and those people sometimes commit the simplest of programming errors indeed!). The doodle guys also considered keeping the code and changing the output to -107 as a reference to debugging (and the moth), but figured that most people wouldn't get the moth reference.

  45. PERFORM LOBOTOMY 3 TIMES. by TheRealHocusLocus · · Score: 1

    My favorite COBOL line ever,

    PERFORM LOBOTOMY 3 TIMES.

    LOBOTOMY rang the bell on the printer without printing anything, we placed the above line at the end of long running procedures to alert the operator.

    --
    <blink>down the rabbit hole</blink>