Slashdot Mirror
Why Does Everyone Hate Microsoft?
MrSplog asks: "I'm doing a short project on Microsoft and its impact on society. A considerable part of this project has been looking into people's perceptions of Microsoft and the heavily negative bias of that perception. Since Slashdot is one of the world's forefront leaders on Microsoft hatred, I wanted to know: just why do you hate Microsoft? Please be as descriptive and as thorough as you like. Counter arguments and positive comments are also appreciated."
Oh, I don't *hate* Microsoft. In fact, I have friends who work there and have made money off of Microsoft stock. I still use Word (although Pages is coming on strong and if I could get EndNote compatibility, I'd switch entirely) and Excel and root for the company on occasion. Where I object to Microsoft is in their shoddy products. Almost every product I've used of theirs that came out at version 1.0 has royally sucked. Their whole concept of bringing products to market is date/deadline driven rather than quality or product driven, much less consumer driven. Classic cases of abysmal products were Windows v1-3, Win-98 and ME, the Zune, Bob, that first tablets and the ultra portable systems I've previewed (error messages that were too big for the display for instance), and of course their always changing interface standards and poor security issues.
Saying all that, I actually had a pretty good Micron PC running Win 95 that was remarkably stable. Of course upgrading it to Win98 was a unmitigated disaster. Win NT was a very stable OS, that was just cryptic to use and administer. Win2000 was pretty decent, and it almost made me switch my home system from MacOS to Win200, but like most products they have simply used their monopoly status to make the right changes very late in the game if ever. How long did it take them to adopt all characters for file names?
Where I really started getting disgusted with their business was after I saw company after company run out of business due to business practices that bordered on illegal and in some cases blatantly crossed the legal line. I always tended to prefer the MacOS, but was fairly platform agnostic (using Windows, Solaris, Linux, Irix, MacOS) for whichever task needed the appropriate platform, but with the advent of OS X, I've become a strong advocate for the Macintosh platform which brings up another issue entirely.... Microsoft has for decades now used Apple as their R&D lab. It's an obvious and well known joke, but if you are familiar with OS X, just wait until you get to play with Vista. Come on now, there are some very smart folks at Microsoft, so why can't they come up with ideas and products on their own? My take on it is that it is an efficiency issue combined with a management issue with too much oversight at the early and mid stages of the game. For instance, how many programmers are there on the Windows development team? Its in the thousands for sure, perhaps tens of thousands all told. For OS X, the number of full on programmers numbers in the hundreds. Under 300 for sure last time I checked a couple of years ago. The whole Quicktime team numbers around 30-40 whereas the Microsoft Media Player team is well into the hundreds. We could go on and on here, but to answer your question, this scientist at least does not hate Microsoft. I've just watched the company for years, purchased some of their products and have found a product from another company (Apple) that meets my needs and does not get in the way of my work the way Microsoft products tend to do.
Visit Jonesblog and say hello.
Before the DOJ case we all used to wonder why they produced such poor quality software at such high prices. In fact, we all felt kinda pissed off and betrayed by this. Then the anti-trust litigation put it all into perspective. No mystery anymore, that is, so long as you have even a basic understanding of microeconomics. Monopolies produce poor quality products at high prices - that's what monopolies do. So yeah, no reason to hate Microsoft anymore, we know what they are. Of course, a number of people are still pissed at Microsoft for their abuse of their monopoly, that's fine. But all those people who are pissed off at the government for handing Microsoft this monopoly they have, well, go be pissed off at the government.
Besides which, they'll be gone in 10 years anyways. That's not a rimshot. Shit, it's not even an original thought. It's just the way things are going.
How we know is more important than what we know.
Here's an example...
When NT was first announced, I thought it was the coolest thing since bottled beer. The protected mode subsystems looked like a way to consolidate the APIs of multiple systems. As smoebody who'd already programmed Unix, PDP-11 (RSX), VAX-VMS, MVS, Univac, CDC, etc in the years prior, I thought NT was going to totally rock. It had the potential to subsume everything around it.
Little by little, the OS/2 compatibility evaporated, X-Windows was declared "brain dead", it went beyond embrace and extend, it became Microsoft's way or the highway.
I still wonder - if MS had supported POSIX / UNIX APIs in a protected mode subsystem, would Linux have really "happened"?
Alan.
...It's contempt. 8^)
Okay, I jest. There are number of very good reasons the like Microsoft - their office automation products do make life easier - but it's just not enough for me. The fundamental problems are threefold:
There's no way to guarantee my work. (This is actually a complaint about proprietary software in general, but Microsoft is the worst about this.) On two or three significant occasions, I have been completely burned after commitments that I made to a client based on technical assurances I'd received that proved to be false. I've been forced into unsustainable situations because there was a huge gap between what the product promised to do and what it actually did. Dealing with the last 20% of any task is difficult at the best of times, but the number of times on Windows that I've been forced to accept that things are never going to run as designed because of shortcomings in the technology... they're too many to count.
Ultimately, the only way I could maintain my professional reputation (and my pride) was to walk away from the Microsoft Windows platform completely and to live with Linux and FOSS. It's not that it's better, per se, but at least I can make things work exactly as they're designed, without being completely at the mercy of someone else's market research and development cycle. In the worst case scenario, I can always keep a client happy by paying someone to provide a patch expressly for them. I may lose my shirt on that contract, but I'll never have a pissed-off client, and in my business, that's golden.
They're holding us back. I did a back-of-the-napkin calculation the other day, to see how much time I'd spent that week dealing with Windows' shortcomings instead of actually improving our systems. It was a fairly direct equation, because I was working on developing a really cool network monitoring toolkit that week. Every hour I spent at someone else's desk cleaning up crap delayed the arrival of this very useful tool by an hour. I calculated that I work 30% slower than I could do if I didn't have to deal with spyware, trojans, spambots etc.
That's insane. Seriously. People who don't know anything besides Microsoft will tell you that exploits happen to everyone, that if it wasn't MS, it would be someone else. But it just ain't so. Today's Word exploit is stunning evidence that Microsoft practices... whatever the opposite of security is. No I don't mean 'insecure'; they're apps are that, but their design is more like 'anti-secure'. I mean, who in their right mind stores pointers for memory move operations in a word processing file?
They are trying to break the Internet. The first points disappointed me, as a geek. But this point makes me angry. For Microsoft, dominance is not sufficient. They don't play to win; they play to destroy. And the tactics they use are bad for everyone. They oppose open systems, protocols - anything that makes it easier for people to share. This selfishness of spirit is manifest in every aspect of their business, and it impacts directly on my ability to do my job.
I don't mind having to explain the relative merits of a FOSS solution to an MS-only one. But when I have to respond to lies that are spread about my stock in trade, I get upset. When I spend more time countering FUD than actually talking tech, I get upset.
This is not competition. This is the opposite. It's playing dirty. It's cheating, and I'm tired of it.
Crumb's Corollary: Never bring a knife to a bun fight.
Personally I think most people here a very good reasons to hate them. I wrote windows software exclusively for over 7 years and still do on occasion. Over the course of those 7 years they did many things that drove me not quite to the point of hatred but more of a awakining. Little stuff like how can I code against the shell? Well it took years for them to disclose that information so that we could add simple extensions to the shell. I am not sure they even disclosed it somebody probably had to reverse engineer the api. They keep all this little stuff to themselves for their own benefit and to lock out competitors. IE oh yea there is another one, they linked that piece of crap into every developer tool, shell everywhere they could stick it not to help me out as a developer but to dominate the browser market. Took their advice, yea make everything run on transaction server it is the greatest, what now I have a ton of shit running on one and transcation server has been dropped.
Once upon a time I developed a proprietary solution to connect up com objects to a j2ee server, guess what happens, I get a call from a microsoft goon one day trying to buy full rights to the
code...why? Not because they wanted to use it but because they wanted to bury it.
How about foxpro? oops they bought that out and buried it, best and fastest desktop database ever
made.
How about visual studio, pretty nice tool but if you use it long enough you will start to find the
artifical walls put up to drive you further to their platform. Easy stuff is easy in visual studio, soon as you want to push the edge you run into some bug, or artificial wall put in your way.
Nope, best thing I ever did is remove them from my personal and professional life.
Got Code?
Microsoft writes lots of drivers. They have drivers for all sorts of standardized hardware with open specs, like OCHI USB controllers. What Microsoft doesn't (and can't short of reverse engineering) write drivers for are pieces of proprietary hardware. The same reason that the only good Linux nVidia video drivers are a binary from nVidia is the reason that Microsoft doesn't write nVidia's video driver either.
Of the 118 driver modules currently loaded on my system, 100 of them are (C) Microsoft Corporation. The others are 5 for VMWare, 2 for my nVidia video card, 1 for the nVidia nForce MCP net adapter, 1 for the Realtek 650 sound, 1 for the OpenVPN virtual TAP adapter, 1 for the crappy Macromedia safedisc copyprotection driver, 2 for Daemon Tools, 1 for Process Explorer, and 4 for the cd burning software. Of the non-Microsoft drivers that are supporting real hardware, that's 4 drivers for 3 devices. There are only three devices on my system that Microsoft didn't write drivers for. If Linux were running on this system, I'd want the binary nVidia drivers for video and networking (AFAIK nForce2 networking still isn't supported in the mainline. It definitely wasn't when I built the machine).
Microsoft definitely has a drivers division.
I do agree about Microsoft fixing the wrong things most of the time in their OS, though.