More Jack Wallen insanity:
Anyone having seen a Microsoft ad knows that Steve Ballmer has likely contracted the entire marketing department to Sloppy Joe’s Publicity Agency in Bumfluff, Idaho. Stock characters half-heartedly talking about stock things are pretty much all that we, as the unsuspecting individuals on the receiving end, have to determine the kind of doodads the Redmond-based company is trying to sell to us. What’s more – it also appears that Sloppy Joe’s has a strict policy of spending no more than three minutes on understanding every item they are trying to promote plus the target demographics that they are supposed to confuse with their messy, unfocused, over-the-top advertisements:
Cloud Vs Claude – Gallery
Sharing photos while chatting? Is that like the Facebook thingy everyone is talking about? Hey, if the ad didn’t spend over 60% of its duration showing what’s-his-face doing utterly retarded crap, I would at least have a better chance to know a bit more about this “cloud” thing it was supposed to pitch.
So much for MS “marketing machine”.
2: Hardware support
The only thing about hardware that Windows actually supports is a binary driver framework – you know, that “stable kernel ABI” thing that Greg Korah-Hartman decides that You Don’t Really Need™? No binary driver framework means that there is simply no way manufacturers can test a driver set along with the hardware and guarantee functionality over a reasonably large user base. But, hey, you can always trust people who know stuff-all about the silicon (like the Linux kernel dev team) to maintain the driver set for you, right?
3: Smart phone syncing
Yeah, why bother using software that your equipment is designed to work with when you can mess around with reverse-engineered plugins and then bet your data on them?
4: Enterprise presence
When I think of enterprise-level SMB support, I don’t usually picture in my head a wonky implementation of CIFS complete with non-existent Access Control Entities management. Sure, I can’t stop Wallen from fantasizing about deploying Samba for any level of usage, but for the rest of us, the idea of replacing perfectly working Windows file sharing solutions with broken, half-baked substitutes from the 90s is just ridiculous if not utterly insane.
5: Workgroup setup
Again, Samba is horrid for just about any level of usage. Not only it completely disregards NT’s user privilege model – it also lacks a considerable amount of features (such as Active Directory replication unless you don’t mind risking with the perpetually-alpha Samba4) to make itself useful within an AD-based domain. Even on a peer-to-peer basis, you will still need to tune your Windows Vista+ machines in order to accommodate Samba’s dated code base.
It just doesn’t work.
X11… Really, do I even need to explain any of that?
Yup, and wait for everyone to return the machines by the hundreds.
To an average consumer, this is what a Linux desktop is like – an OS with almost no support for any new hardware, shaky behaviors with multimedia, a library of mostly worthless applications and migraine-inducing interactivity laden with command-line arcana.
You might as well go and sell this instead.
But what happens when you buy that shiny new computer, wipe off Windows, install Linux, and have a problem? Most likely, you’re going to hear that you have invalidated the warranty or support contract by doing so. PC makers need to learn to support the Linux operating system.
Why? Just, why?
9: Software installation
New users expect to be able to download a single file and double-click it to install.
Again, binary compatibility plays a major role in this sort of things, and that means whoever building the OS will need to expend time and energy on tediously designing and implementing a framework encompassing potentially thousands of run-time libraries and countless backward and forward issues. Seriously, take that to the packagers of your favorite distro and see if they care.
10: Direct X
Yeah, and what did you say about hardware support again, Jacko?