Yeah, I get that. Fortunately for me, having dealt with enough a-holes who got hostile with me when I was trying to help them solve their PC problems (which often were of their own creation), I've mastered the art of being the exact opposite when I'm the one getting the support. I've gotten a lot of extras and freebies that way, too.
The guy I spoke to at the most recent service center I called definitely spoke my language. We hit it right off. In fact, if I do decide to buy a Mac, Ill drive to CT to make the purchase through him. I like to early on kindle good relationships with people I may need in the future.
The next step in my decision-making process is to find someone I know who uses the Adobe software I use on a Mac so I can get a feel for how it works. That won't be hard, but it will necessitate a trip, probably to The City. But I'm about due to visit some people there, anyway.
Of course, there's also the chance that MS may come to their senses regarding the spyware and forced updates, and thus defuse my annoyance at them. Those are really my biggest objections to 10. I really don't have a problem with Windows itself. Since Win7, it's been absolutely trouble-free for me; and even before Win7, I knew and could avoid its pitfalls.
Even WinNT/2K were rock solid for me. They just were somewhat limited in their functionality, particularly with regard to multimedia work, because of the lack of VXD support. XP was a start in unifying the functionality of the 9x and NT lines (well, actually Me was the first attempt, but that was an absolute disaster), but MS didn't really get it right until Win7.
In truth, my annoyance at MS with regard to 10 has to do with a shift of attitude on MS's part more so than anything I couldn't work my way around. I already make multiple, redundant backups and clones of my systems and I know how to disable the spyware. I just don't like the fact that MS is becoming another Google or Facebook whose business model includes selling their users' lives to the highest bidder. I also don't like MS assuming a paternalistic role regarding updates for which experience clearly shows they're ill-suited. Too many of their initial update releases break stuff for me to unhesitatingly let them update my system without notice.
My policy with regard to updates, with the occasional exception of updates affecting zero-day security exploits, is to wait a bit and see if other people report problems with the updates as relates to the software that I depend on. They do cause problems often enough that I've found it prudent to wait. Very often they'll release an update to the initial update that fixes the problems a few days later.
I also refresh the clones before any updates just in case they hose the system in a way that I can't quickly fix. The clone drives are offline except when I update them to protect them against cryptolocker-type exploits, so I need to know when updates are going to be applied so I can manually refresh them. I also have incremental images and data backups stashed in multiple places, but a fresh clone is the easiest and fastest way to restore. Keeping it safe requires it to be offline most of the time.
I've also looked into and abandoned the Hackintosh idea. That, from all I've read, is absolutely not the way to go if what you want is a trouble-free experience. Yes, I could replace failed hardware myself; but software-wise, keeping a Hackintosh system working properly requires perpetual hacking. It would completely defeat the purpose of what I want to do, which is to avoid downtime. It might be nice for hobbyists, but not for a production machine.
I feel comfortable now that I can make the switch to Mac if MS continues to **** me off. I also may find that I like the experience using DW, Fireworks, and Illustrator on Mac enough that I switch just for that reason. Finally, I'm lurking on the Adobe support boards for Mac to get a feel for how often problems arise using CS6 on that platform and how quickly they're resolved.
I have a hunch that what I'm going to do is offload my working data to a local Linux server (maybe using OwnCloud, which I've been itching to play with anyway), buy a Mac, and join both my Windows and Mac machines to the server. That way I can still work in Windows on rush jobs when I don't have time to fart around learning how to do the same things in Mac that I can do in Windows. It will help ease the transition.
Rich