Slashdot Mirror


The 87 Lamest Moments In Tech, 2000-2009

harrymcc writes "The last ten years have been an amazing era for tech — and full of amazingly dumb moments. I rounded up scads of them. I suspect you'll be able to figure out which company is most frequently represented, but Apple, Google, Twitter, Facebook, Sony, and many others are all present and accounted for, too."

29 of 328 comments (clear)

  1. The very lamest moment? by Anonymous Coward · · Score: 5, Funny

    Wouldn't that be the "first post" ?? :)

  2. sony rootkit by Anonymous Coward · · Score: 5, Informative

    http://en.wikipedia.org/wiki/sony_rootkit

    never forget, never forgive

  3. obligatory by farlukar · · Score: 3, Informative

    decade = 2001-2010

    But at least they didn't make it a 87-page article.

    --
    Ceci n'est pas une .sig
    1. Re:obligatory by Mononoke · · Score: 5, Funny

      Yeah, how /do/ people pronounce this decade?

      The naughties.

      --
      NetInfo connection failed for server 127.0.0.1/local
    2. Re:obligatory by Anonymous Coward · · Score: 5, Informative

      technically a decade is any ten year period, doesn't matter when it starts

    3. Re:obligatory by Ren+Hoak · · Score: 3, Funny

      decade = 2001-2010

      You aren't a coder, are you? If so, I envision many off-by-one errors in your work.

    4. Re:obligatory by dkh2 · · Score: 5, Insightful

      Actually, he has it right. Our modern, western notion of a calendar is marred by the fact that the Romans had no concept of zero until the conquest of Spain and the ensuing interaction with the moorish people who lived there. Thus, we start counting dates with 1, not zero. Therefore, the '60's is the decade beginning immediately after the end of year xx60 but a person "in their 60's" has completed 59 years of life and not 10 more.

      In our Christian era calendars you do not find a year zero. To our modern, mathematically educated minds that would have been the year before Jesus of Nazareth was 12 months old.

      Of course, our calendars, while allegedly based on the birth date of this man Jesus, are flawed by many other issues. Among these are:

      1) We don't actually have agreement about the precise year of Jesus' birth.
      2) The 25-December customary date is a fabrication. Jesus was most likely born in the spring based on accounts of what was happening at the time.
      3) Our calendar system has been changed a few times over the past two millennia.

      --
      My office has been taken over by iPod people.
    5. Re:obligatory by asylumx · · Score: 3, Funny

      Seems like this problem would have been solved a hundred years ago...

    6. Re:obligatory by Anonymous Coward · · Score: 3, Funny

      So I guess the first decade ran from -1 to 0, and the second decade was from 1 to 10?

      These decades go to 11.

    7. Re:obligatory by larry+bagina · · Score: 3, Insightful

      The 60s ended in 1974.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    8. Re:obligatory by ari_j · · Score: 3, Funny

      Hey, I have to do something with all the time I am refusing to think of the children!

  4. Playstation 3 backwards compatibility and price by assemblerex · · Score: 4, Funny

    "If anything it's too cheap" That didn't go over too well did it now.

  5. First Paragraph by datajack · · Score: 5, Insightful

    When clocks struck midnight on January 1st and the dreaded Y2K bug turned out to be nothing but a mild irritant, it proved once again that the experts often don’t know what the heck they’re talking about.

    No. The Experts were the ones working many, many hours in the preceding years fixing and updating things so that when the clock did turn, the problems were - for the main - no longer present. A job damned well done and the people fixing it should be praised, not ridiculed.

    The people who don't know what the heck they were talking about are the media types like this guy who are quick to jump on catastrophic failures but rarely (if ever) give due praise when things are planned and done right. "Everything's fine" doesn't make good headlines for these people.

    1. Re:First Paragraph by Viol8 · · Score: 5, Insightful

      You complete dick.

      I was working in a bank at that time. If we hadn't fixed our systems then come 1/1/2000 every customer in our business area would have found all their transactions failed as the system would have thought they'd expired 100 years ago!

    2. Re:First Paragraph by Gadget_Guy · · Score: 4, Informative

      Could you please point out a single example where a catastrophe was avoided due to fixing the code handing year changes?

      How would we know? It is not as if people are going to publicise the bugs that they fix. "Hey everyone, we almost nuked Poland!"

      Anyway, the worst of the hype that went around did not come from the experts. Nobody who knew what they were talking about would have said that there would be starvation in the streets. That said, there were definitely some people who tried to cash in on the paranoia. We had some consultant come in and try to sell us software to fix our systems because they were not Y2K ready. Sure enough, when the year changed the computers wrapped back to 1981. However, resetting them to the correct year worked fine.

      But just because some unscrupulous people jumped on the bandwagon doesn't mean to say that there were not real bugs to fix. The main software that we wrote had a Y2K bug in it, but we fixed it back in 1997 without fanfare. Just because you never heard of it being fixed doesn't mean to say that it was a made up bug.

    3. Re:First Paragraph by smpoole7 · · Score: 3, Insightful

      To this (and the other replies here): he's not referring to people like you. Don't think that for a minute. I was a Y2K Fear debunker myself, and I assure you, I NEVER attacked people like you who WERE working around the clock to ensure that the transition was smooth.

      What I attacked -- and what he's clearly referring to -- were the outright fearmongers. "We CAN'T fix it all in time, buy beans, bullets and head for the hills!" ... and ... "embedded systems are the great unknown, we're all going to die, so buy beans and bullets and head for the ... etc., etc." Have you forgotten the "Y2K Crisis Center" (or whatever they called it) with Sam Donaldson, on watch over the transition? All of the newspaper articles in early 1999 about how the End Was Coming?

      THAT'S what he's referring to. Of course there were bugs to be fixed -- some of them true showstoppers. Yes, a lot of people like you poured a lot of nervous sweat into fixing them.

      But personally, speaking for myself, I'll never respect Ed Yourdon again. He was the ringleader of the "too many lines of code, it CAN'T be fixed crowd," and continued to ringlead even after it became obvious that it WAS being fixed.

      Not you, poster. You did a GREAT job just so that "debunkers" like me COULD say, "it'll be a non-event." :)

      --
      Cogito, igitur comedam pizza.
    4. Re:First Paragraph by betterunixthanunix · · Score: 5, Insightful

      What this chapter completely misses is that the emergency spending on Y2K fixes was just the tail end of a long effort of companies updating their software. Journalists were not talking about the Y2K bug in 1991, but plenty of programmers were already aware of it and already working on solutions to the problem. By the time the story got interesting -- as the year 2000 approached -- the problem had been mostly solved without any prodding from the media or pushing from the president. This whole situation was compounded by the fact that most people, including the journalists covering the story, had no understanding of how computers stored dates, and the fact that companies whose products had nothing to do with the Y2K bug were advertising their software as "Y2K compliant," and everyone wound up thinking that there was impending doom.

      For the record, the Y2K bug did actually threaten critical computer systems, many of which were mainframes installed decades earlier, but those systems were fixed long before the story ever ran on the news.

      --
      Palm trees and 8
    5. Re:First Paragraph by betterunixthanunix · · Score: 4, Insightful

      I had an uncle working for MetLife in the early 90s; had he and his team not put in many months of work back then, the Y2K bug would have left millions of insurance claims unpayable, from business insurance to health plans. On any given day, thousands upon thousands of insurance transactions are processed automatically by a computer, which would have rejected everything as invalid because the claim dates would have appeared to be before the policies were opened.

      People who think Y2K was not a big deal were either children when the problem was solved or never really understood the problem to begin with. Y2K38 is the next big date/time bug to deal with; many people here on /. will probably wind up working on fixing the problem long before it causes catastrophes, and we will be pretty old on January 1, 2038. I am also pretty sure that people like you will be saying, "There was never really a problem" for many years afterward, and someone like me will probably have to reply with a story about a relative who solved the problem before the press started running stories about the end of the world.

      --
      Palm trees and 8
  6. Yay, another weirdly huge list. by jault · · Score: 5, Insightful

    You know, if that number was smaller, I might actually click through & read the article. But 87? Really? A number that large makes me think that you just wrote down every single lame thing you could think of & didn't edit at all.

    Personally, I'd prefer a much shorter list which someone made some effort to pare down to the moments that were genuinely the lamest.

  7. Y2K by ernst_mulder · · Score: 5, Insightful

    From TFA: "When clocks struck midnight on January 1st and the dreaded Y2K bug turned out to be nothing but a mild irritant, it proved once again that the experts often don't know what the heck they're talking about."

    Well, that kinda hurts.

    I was responsible for a newspaper ordering system that definitely would have stopped processing orders in 2000. Cost quite a number of man hours. The majority of the Y2K my team had to solve weren't for the year 2000 but for passing into the year 1999 because many ordering systems had stupid (year+1) counters internally. It was a very stressful period and I very happy it went the way it did without major disasters.

    The experts that didn't (and don't) know what they are talking about are the ones thinking you can upper-limit a year counter at 1999 (or 2039).

  8. KDE 4.0 and KDevelop 4 by tjstork · · Score: 4, Insightful

    KDE was flying high with its well regarded 3.x version, and then its developers disappeared with lustery promises of how great KDE 4 would be, and emerged to ship a completely unfinished product. Things are better with KDE 4.later, but, KDE 4.0, wow, you are rough. Meanwhile KDevelop 4 still doesn't work, and has been eclipsed by, well, Eclipse.

    --
    This is my sig.
  9. Agreed by Viol8 · · Score: 5, Insightful

    At the company I worked in at the time there were double digit year records used all over the place. If we hadn't fixed the code the whole system would have falled over come the millenium.

    All these arsehats who go on about the Y2K being a load of scare mongering paranoia are the ones who don't have a clue about just how much work went on in 1999 trying to sort the issues out!

  10. #83 isn't lame, it's accurte. by pthisis · · Score: 5, Insightful

    From TFA:

    83. And Taco Bell was never a taco company.
    In an interview with the New York Times conducted in the wake of Yahoo’s decision to outsource its search features to Microsoft, Yahoo boss Carol Bartz says that Yahoo has “never been a search company.”

    Carol Bartz is correct--Yahoo started out as a link collection, then a hierarchical directory (basically like http://www.dmoz.org/ then added a lot of portal services (including email, stock quotes, etc).

    The thing that they never had, until 2004, was a search engine; Yahoo put other company's searches on their site (including Inktomi for a while, and then Google up until 2004). Doing that with Bing is just returning to what they've done historically.

    --
    rage, rage against the dying of the light
  11. Twitter by jo42 · · Score: 4, Informative

    ##. Twitter

    Nothing else need be said.

  12. Thanks to the Y2K heavy lifters! by LaminatorX · · Score: 3, Insightful

    I for one want to celebrate the anniversary of the Y2K Bug's passing by thanking all the people who's hark work kept it from being far far worse than the few mild annoyances we experienced. The word I saw was some gas pumps that were locked up, and it could have been far worse if a whole lot of coders and analysts hadn't spent a ton of time pouring over reams of old code and fixing problems. Double thanks to all the Grampa Geeks who came out of retirement to show the kids how COBOL was done and why it's still so important even ten years later. A nod goes even to the suits at the top who looked beyond next quarter's numbers and funded the stitch in time would save nine.

  13. Meta-answer by dkleinsc · · Score: 4, Insightful

    #88 - the point when every news organization feels compelled to make really long lists of the top ____ of the last decade. It's like the annual "top ____ of the year" lists, only 10 times as lame.

    --
    I am officially gone from /. Long live http://www.soylentnews.com/
  14. Re:Google C&Ding CyanogenMod by phillymjs · · Score: 3, Informative

    Meanwhile Microsoft actually has a good reputation for turning a blind eye to people making roms for Windows Mobile.

    Turning a blind eye to piracy and other stuff you'd expect them to fight against is a standard Microsoft tactic in markets they want to take over. In their mind, as long as you're using a Microsoft product, even if you stole it, that's better than you using a competitor's product.

    Once they are the de facto standard in a given market, that's when they begin finishing off their weakened competitors and turning the thumbscrews on their users. That's why you could pass around Windows install keys for years with impunity, and then XP got activation. Once the activation-free corporate XP keys got out, they had to turn the screws some more, and now even corporate copies of Vista and, I presume, 7 require activation of a sort. People might find ways around that, but the point is Microsoft is making it more and more difficult to avoid paying them for Windows now that they've sewn up the OS market.

    Of course, I could have made this post a lot shorter by comparing them to drug dealers: "First one's free," then once you're hooked, up goes the price.

    ~Philly

  15. Re:Intel making Microsoft lower specs by UnknowingFool · · Score: 3, Informative

    The issue was MS told hardware makers for a long time what the minimum spec for Vista. So they designed their PCs around it. The minimum was going to be more costly if they didn't use Intel's GPU. However at the last minute they changed their minds under coaxing from Intel who would have a large inventory that wasn't compatible. This infuriated hardware makers as their plans were suddenly changed. Internally some MS employees knew this a huge mistake but no one with any authority did anything about it.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  16. Re:The XBox's need more coverage. by Again · · Score: 4, Insightful

    - The Gamecube: everything about it. A nasty, tacky piece of junk with no games worth looking at that was put out with the intention of being a serious contender and rightly consigned to third place.

    The Gamecube sold 22 million units and the original XBox only sold 24 million. Nintendo made money off of every single unit sold. I wouldn't call it a failure.