IBM Desktop Linux Pledge, One Year Later

Blue writes "It's been more than a year since the bold announcement from IBM that they planned on dumping Windows for Linux throughout the company. InfoWorld is reporting that not all is well with IBM's desktop Linux push. What went wrong?"

Comments

Re:SLASHDOT'S DESTRUCTION IS FORSEEABLE...

[randallpowell]

I need marshmellows.

Is Slashdot burning in fire for it's sins against Linux or it's sins against EA? I'm not sure anymore. All I know is that we make mistakes and we need to learn from them. The know we learn, the better we become. It's time for forgiveness for our mistakes and come to terms about our differences. We're each special. AMD, Linux, Nintendo, et al are special and deserve respect. We must love each other in unity while tolerating our differences.

Disclaimer

[Ambient_Developer]

Disclaimer (Open Source In A Nutshell): This document is licensed under GPL. You may make modifications to this document, some of which include smiley faces, sqwiggly lines, and other things which have absolutely no bearing on your life yet you do them because you have 30 seconds to waste. If you modify this document you must show it to all your friends, even if they don't want to see it. You must make your modifications to this document publicly available. The most efficient method of making this document available to the public is taping it to your forehead. Although if a strip of tape is unavailable at the moment; other methods will also suffice, such as posting it on the net.

Re:Maybe 'cause they can't read Slashdot

[dedazo]

This is not a Slashdot problem, it's a rendering problem in Firefox. I have the exact same problem you're seeing at work, but not at home - with the same 1.0 build of the browser. Why? I have no friggin' idea. OTOH, Mozilla works fine on both boxes. On my Linux laptop FF 1.0 renders Slashdot just fine.

There are two problems here. One is Slashdot's table-laden circa 1996 crappy HTML, which if nothing else should be fixed. They've already been shown how they can save gigabytes of bandwidth (and ergo, $$$) by moving to a cleaner layout + CSS that looks exactly the same. But they know better than everyone else and they drink gin and tonic, so what do I know.

Second it's the Firefox people's position that there is no bug, because they can't reproduce it. We are all suffering from mass hallucination or we're just trying to "damage FF's reputation", as someone told me on IRC a couple of weeks ago (I shit you not).

Re:Maybe 'cause they can't read Slashdot

[dedazo]

Why the lie?

Spare me the theatrics, I hadn't visited the bug page in a long time. It was first denied, then tacked on Windows (see the other duplicates) and then finally fixed and never merged into the 1.0 release. On irc.mozilla.org the whole thing was even worse.

Too much of Mozilla goes like that. They make a good browser, but sometimes they can be hard to deal with.