Excuse me, what? Are you just making this up because you're in a Windows free zone where you can say anything bad about Windows and people will just clap their hands? I've been using Windows since 1992 and I have never seen an update break anything. Yeah, entirely new versions like Win2K, XP, Vista etc would initially have issues with older software, but subsequent maintenance updates would only FIX stuff.
The notion of minor updates breaking stuff wasn't on my radar until I got my first Mac in 2004, noticed weird stuff going on, started googling and eventually found my way here, where I discovered that there's a whole subculture around things that break with every update. There was virtual pandemonium here after 10.5.0 was released and people were having all sorts of crazy problems, like the infamous 'blue screen of birth'... try googling for "back to Tiger" and then "back to XP" and you'll find by comparison that the number of hits for the former is disproportionate to the Mac's market share by about 2 times... And while you're at it try "Vista broke..." and "Leopard broke..."
And even now at 10.5.3 there are all sorts of threads like "list your broken apps here", kernel panic this, endless boot loop that...
Windows certainly deserves most of the bashing it gets, but you're totally throwing stones in a glass house on this one.
Hmm not really from my experience, lets consider the facts since I use both Windows and Mac, and had been a Windows user since 3.1.. Since we are talking about Windows here that started this argument, I will mostly stick with that.
On the mac end, I never had an issue. I am new to mac for about 2 months now (owning one that is, I used other macs before - but mostly borrowed them), and every update my macbook asks me to download never broke anything, and I never experienced the problems that mac people seem to complain about on macrumors (and I use Windows for 8-12 hrs a day for work. at the same time I am also doing stuff on my mac, since I converted most of my documents to that laptop - then when I am done work, I am working on my mac for church and home stuff [videos, internet, bouncing between parallels and mac os x for different apps, doing my homework for seminary, touching up photos for people, etc]. So either I have been extremely lucky or reality has not hit in yet. My mac is a dream as compared to windows, and i have only been using it for 2 months regularly now.
Now back to the windows point of view - which was the point of my post. and I must say one thing, it seems that the problems that plague windows updates are only getting worse. I do not recall all these problems with windows updates a few years ago. I am wondering since MS really did not want to support XP anymore, they are getting slack with what they put out. XP used to be rock solid for a number of years and office was great up until about the middle of offfice 2003.
Here is just a short my list of complaints that started occuring with Xp and Office and you will see why I have issues with Windows and the fact I have yet to have an issue with mac is why I posted what I did:
1. Security update that introduced IE7 - Websites are no longer being displayed properly. you program a website - it looks fine in Safari, fine in firefox, however IE7 scued the display, especially in tables. Another bad issue with IE7, is that for a long time password windows were treated a pop-ups which locked alot of people out of websites.
2. Update loaded last night and cause my system to reboot. my virtual machines (which recieved the same updates) run much slower. One stopped functioning all together and I had to reload it.
3. This morning I could no longer cut and paste from word to outlook, had to reboot. Tihs was on my main desktop and not a virtual machine.
4. Every set of updates in the last 2-3 months locks up my wife's XP media center edition. On my work XP Pro computers I keep losing the sound in my trillian IM. Because our company has all its employees remotely working from home, IM is a vital part of our communication.
5. During one of the last updates to our server, Exchange stopped functioning and we had an email outage for 2 days. Not good when all employees are remote and rely on emails.
6. XP SP3. MS decides to discontinue the /console command when using remote Desktop to log into a PC in console mode. It was replaced with /admin. This is a pain when you support over 200 hospitals (and growing) and have all the RDP connections to multiple PC's and servers saved - so you do not have to enter the IP and password everytime; all you have to do is double click the RDP. Every one of the RDP's that used /console had to be revisted.
7. During one of the lovely updates (and not service pack 3 either), I now get a message in RDP when I try using /console (I even tried to use /admin thinking I got sp3) that this is not a valid computer name. Since I cannot RDP in console mode, I have to pray that mstsc works. On Windows Server 2000, mstsc is not supported, so you are out of luck.
8. During an office update, 3 of my critical automation macros were broken and I had to reprogram them.
10. During one of the updates all my trusted websites in my IE were wiped out.
11. During one of the updates, RDP in 2 of my vurtual machines recieved corrupted Dll's and I had to copy them from my main desk top.
12. more than once I was working in the middle of critical applications and an update loaded. the little restart now or later window poped up behind another window and did not appear on my task bar. This caused my system to reboot in the middle of working on an emergency room interface. Since my system did not reboot cleanly, I had to fix my system and left an emergency room/Lab Interface down for 1/2 an hour.
13. One morning after an office and windows update, I found that all my rules in outlook disappeared, so instead of my junk mail going to my junk folder, alerts going to another folder, etc - I had over 1000 items in my inbox I had to sort through to see what needed addressing now. It took me an hour to re-setup my rules and have my mail going to the right places again.
14. An update to office 2007 cause the business contact manager for outlook to get messed up. It would no longer allow outlook to start up, and I had to uninstall office and reinstall it. This time I did not install business contact manager. every update in office or windows would cause it to get corrupted.
15. I worked for a company last year where an "automatic update" took down a critical server. they had to go back to a restore point, which meant they had to reload data for the applications loaded.
16. When IE7 came in a critical update, all of our web-based applications in a company I worked for stopped working. We had to revert back to IE6 to get customers up and running. then it toook a year to get them straightened out to work with IE7.
17. I had an automatic update corrupt one of the critical operating system files in the WIN32 system folder. In order to save what was on that PC, we had to pull the hard drive and put it in another as a slave and copy off everything. Then we had to format the hard-drive, reload windows, and then copy everything back.
Whew - that was just the last year of so of my memory. Like I said, it seems that only in the last 2-3 years XP updates have wrecked havaok in my life.
Also, tell me why in the MS world, if I have load 2 PC's with office (no plugins on either), and create an access app it works fine, but when I copy it to the other PC and try to run it, it tells me I have missing stuff?? Both PC's wre loaded exactly the same with Office 2003. the only difference is if you look at help, about, and get the version number - the last digit is off. So if you think you got office 2003 and it is compatible with other office 2003's you better think again.