first off, i didnt write this, found it on linuxsucks.org, very good reasons and u can do a whole load of research on what this guy says, it will take about 30 mins to read it but is well worth it, so from now on when some calls u nerd that has no idea why u hate microsoft, u can start quoting
much of it u already know, but u will be suprised
well anyway, here it is
why to hate microsoft
Why is it that Microsoft's products keep mushrooming in size with each new release always requiring significantly more disk space and more processing power than the last time? They might claim it's because of all the new features they add each time, but that's only half the story. The new features and the increased processing requirements are designed to fuel the process of perpetual upgrades. This is Microsoft's way of rubbing Intel's back so that Intel will give Microsoft preferential treatment when it comes out with new chip specs. It's also Microsoft's way of convincing consumers that their newer product versions are better because they are so much bigger. Their new features are often superfluous but users must still deal with the overhead required by the features even though most will never use the features.
* CNN has a good article which explains why bloat is such a bad thing. Unneeded features make products more cumbersome to use and the addition of new features often sacrifices the performance (and sometimes the integrity) of older features. Why not stick with an older version of the product then? Two reasons: (1) you only get customer support if you stay current, and (2) if you need to work with other people using the same program older versions are often incompatible with newer versions, so if anybody is using the newest version, then everybody must upgrade.
* "The Bloatware Debate" is a technical discussion of how two separate people dissected one particular Microsoft program and found out, to their shock, that it was over 2,000% larger than it should have Been. It would appear from this discussion that the cumbersome size of Microsoft programs is due not only to the continually growing clutter of useless features but it is also due to careless programming (perhaps to an even larger degree).
* Did you realize 486's are still useable machines if you're running something other than Microsoft's latest software? For instance, Linux worked great on 486's back when they were the top of the line and amazingly enough it didn't stop working on them once the Pentiums came out. Yes, Linux has evolved since then to take advantage of more powerful computers, but the latest version of Linux will still work well on older equipment. There are also plenty of other operating systems that work equally well on machines that Microsoft has abandoned support for. Don't let your old equipment gather dust - older machines make great IP Masquerading routers (which allow you to connect multiple computers to the internet at once using only one phone line or cable modem) or great machines for checking email and chatting online. If you can't use your older equipment yourself, rest assured that somebody out there (such as your local school) could put it to very good use. Don't write it off because Windows doesn't run on it.
Also contributing to Microsoft's goal of putting everybody on a perpetual upgrade cycle is the backward incompatibility in Microsoft's products. Once a small number of users adopt a new version of a Microsoft product all other users are pressured to upgrade lest they are unable to interact with files produced by the newer program.
* Dan Martinez summed up the situation created with the incompatibility in subsequent versions of Word when he said, "while we're on the subject of file formats, let's pause for a moment in frank admiration of the way in which Microsoft brazenly built backward-incompatibility into its product. By initially making it virtually impossible to maintain a heterogenous environment of Word 95 and Word 97 systems, Microsoft offered its customers that most eloquent of arguments for upgrading: the delicate sound of a revolver being cocked somewhere just out of sight." (cited from the quote file) For a more detailed lament of how Microsoft likes to pressure its customers to keep buying the same product over and over by using backward incompatibility, see Zeid Nasser's page on "Forced upgrading," in the World of Word.
Discuss this article in the Feature Articles area of our forums!
It's pretty obvious why the concept of perpetually upgrading is a bad idea for consumers. Perpetual upgrading encourages Microsoft to ship bug ridden products because they can always charge for the upgrade after the bugs are fixed. Case in point, Windows 98 is essentially a bug fix for Windows 95, but those who paid for Windows 95 still have to pay for what should have worked right the first time they bought it.
Whenever Microsoft spies yet another potential market which it thinks is ripe for taking over it generally announces its intention to move aggressively into that market. Microsoft frequently announces new products for these markets that they will ship soon regardless of whether or not they have any genuine interest in actually shipping said products. What this frequently leads to is that people stop buying software in this market because they want to wait for the Microsoft version. Unfortunately if Microsoft sees the market drying up they usually just walk away and never deliver their promised products. The end result is that the small software companies in these markets take a very big hit and frequently go under while consumers end up without their promised product.
* Caldera has an excellent description of how Microsoft uses vaporware to "curtail adoption of competitive products by deceiving end users" along with an unfortunate example of how Microsoft's blatant lies led to consumers foregoing the adoption of a superior, available product in anticipation of Microsoft's non-existent product (i.e., a DOS-less consumer Windows which still doesn't exist as of this writing [August, 2000], well over half a decade later). Caldera's entire paper is highly recommended reading.
Hostile treatment of customers
In the past, Microsoft has fueled its amazing growth by leveraging its way into new markets in order to acquire new customers. The problem that Microsoft has been facing recently is that they have come to dominate so many different markets that there are not enough markets left (where they can leverage their monopoly power) that can be captured for the purpose of sustaining the growth that their shareholders require. Consequently, Microsoft has turned its sights back on its existing customers. Microsoft is finding creative ways to wring more money out of its existing customers, often times with hostile results. Now is the time to switch to Microsoft alternatives so that you can escape the Microsoft auditors who can make more stringent demands on you than the IRS (because you agreed to these demands by accepting Microsoft's EULA, or End User License Agreement).
* One example of Microsoft's hostility to its existing customers came in September, 2000. Microsoft demanded that the Virginia Beach government account for all copies of Microsoft software that were in use within the government and provide proof of purchase for each product. The reason? "Nick Psyhogeos, a Washington, D.C.-based attorney for Microsoft, said the firm has found that government agencies sometimes inadvertently acquire counterfeit software." There was no mention of a reason why this particular city government was singled out -- they were not investigated because of something which they did to arouse suspicion, but simply because they were a large organization that Microsoft hoped they could frighten more money out of. The city was presumed guilty until proven innocent and this cost the tax payers a great deal of money as the city reassigned 25 percent of its technical work force to work specifically on the task of generating the information demanded by Microsoft.
* Microsoft has recently added "features" to its software in order to prevent unlicensed use, and users are already crying out at the negative effect this has had on usability and reliability.
* David Coursey from ZDNet has written about his personal experience of being deprived of the use of his legally licensed Microsoft software at the worst possible time because of Microsoft's over-zealous "anti-piracy" measures.
Microsoft tends to kill off competition by drawing on resources supplied by its OS monopoly to completely out-spend its competitors, by using its customers' dependence upon existing products to force new products upon them, or by buying its competitors outright. Probably the most publicized (but definitely not the first) example of Microsoft's leveraging of their monopoly power to take over new markets is their dealing with Netscape. Microsoft spent millions of dollars creating a competitor to Netscape's web browser and then gave away the browser for free in an attempt to drive Netscape out of business. Not only did Microsoft give its browser away for free but it also spent money on promotions so that people who switched to their browser would get other things for free -- Microsoft was essentially paying people to use their web browser. Microsoft would not have been able to do this if it did not have a monopoly on the OS market and Netscape had no possible business defense on this because you can't make money when you have to pay people to use your products.
To make matters worse for Netscape, Microsoft used their influence with full force to prevent OEMs (an OEM is a computer maker such as Gateway or Dell) from putting Netscape on any of the computers they shipped. Microsoft told OEMs that they could not uninstall Internet Explorer and install Netscape's Navigator even when customers asked specifically for Netscape or they would lose their Windows licenses. For OEMs, losing their Windows licenses would essentially put them out of business, so they had no alternative but to submit to Microsoft's demands. So, Microsoft used their absolute control over something that OEMs couldn't do without (Windows) to push a totally unrelated product (Internet Explorer) into more places than customers wanted and keep other products (Netscape Navigator) out even when that's what customers wanted and what OEMs wanted to give them.
Finally, Microsoft has a habit of killing off competitors by either buying them or their technologies. Once again, a good example of this is shown with Microsoft's foray into the web browser market. Microsoft was late to catch on to the fact that the web was going to revolutionize the way people used computers and once they finally woke up they were dangerously close to having their Windows monopoly destroyed by the greatly reduced importance of operating systems that a web based paradigm would produce. They needed to do something fast. They allegedly tried to carve up the market with Netscape by getting Netscape to agree to stop making Windows web browsers while Microsoft would only make Windows web browsers. Fortunately for consumers, Netscape did not agree to the deal and the web was saved from becoming a Microsoft only technology as surely would have happened. But this made it even more urgent for Microsoft that they reign in this new market right away while it was still time. Lacking any decent technology of their own, Microsoft licensed the Mosaic web browser from Spyglass which they turned into Internet Explorer. So the weapon that Microsoft fashioned in their attempt to defeat Netscape wasn't even their own, but technology they bought from someone else. This was not a one time thing, but a recurring habit of reaping the rewards for other peoples' work which started way back in the beginning when Bill Gates bought DOS (no, Microsoft didn't even create the product that was the seed for their entire monopoly).
* Here is a fairly complete list of all the companies and products that Microsoft has swallowed with its ever increasing appetite for total market domination.
* Yes, Microsoft royally screwed over Spyglass by licensing their code and then turning around and giving it away for free. This obviously made it a lot more difficult for Spyglass to sell other licenses since their potential customers could just embed Internet Explorer for free. Not only did Microsoft destroy Spyglass' existing market, but Spyglass also accused Microsoft of not paying the required royalties on the code that they licensed. Spyglass has since been relegated to a niche market, and it is interesting to note that they don't even mention Internet Explorer as one of their accomplishments in their showcase.
* Microsoft forced major internet web site operators to agree not to promote Netscape Navigator and to forego any business relations with Netscape if they wanted featured placement on the Windows desktop. Yes, you read that correctly -- Microsoft didn't just ask for preferential placement of its own products, it demanded that its competitor's products not be promoted at all. So the next time you hear Microsoft say that they are for consumer choice, be aware that they are lying through their teeth.
* Even the mighty Compaq feared Microsoft and curtailed business relationships with Go Corp and Netscape under pressure from Microsoft.
Bundling of inferior products
In a desperate attempt to try and kill Netscape, Microsoft "integrated" its browser into its OS (well, not really, but that's what they claim in order to get the US DOJ off their back). What this meant for Microsoft was that they got to keep their monopoly for a little bit longer, but it had much more dire consequences for consumers. It meant that consumers were now stuck with a very buggy browser and file system viewer because Internet Explorer was such a rush job.
The buggy browser wouldn't have been too terrible since most people were still smart enough to use Netscape anyway, but Microsoft replaced the standard Explorer (the file system viewer) with IE which left users nowhere to hide from the bugs. If you use Internet Explorer today, be aware that for a significant period after it was introduced, it was very unstable and clearly inferior to the competition, but if you wanted to use Windows you had to use IE anyway because it was made a core part of the system (i.e., the file viewer). The lesson to be learned is that by using Microsoft products you are putting yourself at the mercy of having pieces of your system which work relatively reliably (by Microsoft standards) ripped out from under you and replaced by something broken and inferior every time they find a new competitor they want to kill.
* The January 16, 2000 edition of the Daily Wrap and Flow gives a good summary of major Microsoft components which were bundled with Windows in order to kill competition and which were clearly inferior at the time of their bundling. Specifically listed are GUIs (in response to Quarterdeck), DOS (bundling practically killed DrDos), disk compression (used against Stac), networking (used to thwart Lantastic, Novell and others), Java (in an attempt to wrestle the language from Sun Microsystems) and Internet Explorer (extremely aggressively bundled so as to obliterate Netscape).
Bugs, bugs, and more bugs
Did I mention that Microsoft's products tend to be full of bugs? I'm sure you know this if you've used any Microsoft products to any great extent. It's pretty sad that people have accepted things like rebooting daily because the OS crashed as a part of computing, but that's probably because they haven't seen the alternatives.
* System administrators who have had experience with other operating systems know that Windows is a nightmare to maintain. For a taste of what these people must suffer through read this insightful usenet posting by one frustrated sys admin. He describes some inexplicable problems that crop up in Windows and the vastly inadequate support that Microsoft provides when they arise. Especially interesting to note is the catch-22 that Microsoft puts its users in by refusing to give technical support when the user follows the instructions in Microsoft's own "knowledge base".
Microsoft's products are notorious for their security holes. Security holes in Internet Explorer and Windows NT have been widely publicized and are now accepted as a common occurrence when announced. The public has become largely desensitized to new security holes which is unfortunate because it means that a widespread attack on users' systems is not only possible but quite easy. If it's not such a big deal for you that security isn't a top priority for Microsoft because you don't keep sensitive information on your computer, think again -- if your computer is taken over it could easily be used for such devious tasks as trafficking child pornography, trafficking pirated software, or emailing death threats to the president. What's worse is that any such activity would point to your computer and you would have no way of proving that somebody else did it because Windows does not keep logs.
With its .NET strategy, Microsoft is essentially attempting to transform itself from a consumer software company into a bank. They want to hold all of your personal information and charge you every time it is used (you will be charged indirectly through the merchant you purchase goods from in a way similar to how merchants must pay the credit card companies each time you make a credit card transaction). This is going to make a bad situation even worse if Microsoft maintains its track record for insecurity. While the consequences of using insecure consumer software are bad, the consequences of using insecure software that manages your financial and personal information are much, much worse. This reason alone should be more than enough to avoid Microsoft's products as their intention is to have .NET permeate everything they release which means that a security problem in an obscure part of .NET could leave all of your software vulnerable even if you are careful about avoiding .NET features.
* This News.com article does an excellent job of explaining the root of a lot of Microsoft's security problems and why there are so many security problems. The basic idea is that old code at Microsoft is continually retro-fitted for uses other than what it was originally designed for and as a result problems which were originally annoyances and harmless bugs become gaping security holes. In particular, Microsoft's retro-fitting of all its legacy code to work with the internet opened up a proverbial Pandora's box of problems.
* Microsoft's problems with .NET started to show through at a very early stage. Hotmail users got a surprise in November 2, 2001 when they learned that simply reading their email left their financial data "wide open" and easy to capture. While experts said that the particular exploit that was used was easy to fix, it nonetheless was the result of a "inherent flaws" that would be a "pretty complex task" to fix. Reference article: [CNet Article]
From a Technical Perspective
It is commonly known that Microsoft's applications are given an unnatural performance advantage on Windows because they take advantage of secret APIs which give them the extra speed they need. It's rather disturbing that Microsoft can't compete on a level playing field and feels the need to tip the field because they own it. What's even more disturbing is that they are willing to sacrifice stability and good design principles by "integrating" applications with their OS just to make their applications run faster.
* One of Microsoft's "standards" that they keep closely guarded and which gives them tremendous leverage is the format of their "doc" files (Microsoft Word documents). There is a good write-up of this at Slashdot.
* This letter to the editor by Jim Dennis (search for "Jim Dennis" within the page) explains how Microsoft uses closed protocols, APIs and file format libraries to maintain its monopoly status and how removal of this advantage would level the playing field.
Mutilation of existing standards
Unfortunately, it's not enough for Microsoft to make up its own standards which it keeps unpublished. It also feels the need to hijack existing standards and break them especially if it will help them keep their OS monopoly. For example, Microsoft felt threatened by the Java standard because it was OS independent so it attempted to twist the standard into something Windows specific, all in the name of giving customers what they want.
* News.com has an excellent article on Microsoft's holy war on Java. Read it and you will marvel at how Microsoft can ever say with a straight face that they do things for the good of their customers. That article is only the beginning, though. Check out Thomas Winzig's site dedicated to exposing Microsoft's Java strategy.
* Whether it was intentional or merely an act of incompetence is unclear, but several Microsoft products were built to output broken HTML (the language used to create web pages). When viewed with non-Microsoft products, the resulting HTML appears to be filled with grammatical errors. John Walker gives a good explanation of the situation on his page containing a short program to fix the problem.
* Kerberos is a technology created at MIT to make it easy for users to securely prove who they are. As an example, instead of having to enter a password for every program or web page you want to use, you would enter your password once when you begin your session with the computer and then Kerberos would take care of authenticating you everywhere else so that you don't have to re-enter your password over and over. This is a bit of an over-simplification, but suffice is to say that Kerberos is very useful and very well designed.
Kerberos, as with most MIT software projects, was made freely available for anybody to use and integrate into their software. In typical Microsoft style, Microsoft took the Kerberos standard (which they got for free, mind you), integrated it into Windows and then changed it to be incompatible with Kerberos on every other platform. If that wasn't enough, they refused to freely release details of the changes that they made so that other platforms could be made compatible with their Windows "extensions." After much complaining from the tech community, Microsoft eventually released a spec for their changes, but in order to access it you had to agree to a license stating that it was a trade secret (yes, they wanted to claim trade secret protection on something they had mostly gotten for free from MIT)! Some people eventually decided to ignore the license and publish what changes were made anyway, which prompted Microsoft to threaten legal action. (Note: Microsoft did eventually allow public access to their changes after much outcry. Nonetheless, their Kerberos implementation still does not allow appropriate interoperability with standard Kerberos software.) Reference articles: [Slashdot article #1] [Slashdot article #2] [LinuxWorld article] [Salon article]
Lack of innovation
It's disgusting how Microsoft portrays itself as the supreme innovator when just about all the technology that it has was copied off of others' previous work. Think about all the major innovations in CS technology and then count how many of them were developed by Microsoft. I count zero. This is because Microsoft admittedly does not enter a market until the potential amount of money to be made in it is fairly large.
* Check out The Microsoft "Hall of Innovation" web page for an ongoing effort to find some technology that can actually be considered a Microsoft innovation.