Originally Posted by IQatEdo
Interesting - thanks.
Perhaps we can reflect again on brentbordelon's words:Originally Posted by brentbordelon
What Microsoft should do is QUIT trying to catch up with everyone else and start focusing on something new and different like they did 20 years ago. That's the only chance they have of ever being as good as they once were.
At least that's the opinion of a 25 year Microsoft developer
All the best.
I forgot one thing and you just made me realize another:1. The new "Win 8 Family" is a "bet the farm" moment for MS.
Fail, and they're stuck with 90% of a fading commodity market which won't integrate as well with other makers' tabs and phones as Apple's do with Macs. Result: A still huge base, but one that becomes a relatively static niche, even if a great big niche, i.e., a grey commodity. Or to extend SJ's idiom, mostly a truck (software) maker rather than a sexy car manufacturer.
And with Apple and HP making not only cool cars and scooters and bikes, but with both also in the hot Pickup Truck biz, MS would basically find itself walled in. And for good measure, if netbooks maintain a meaningful presence, Google's Chrome-powered "Netties" will be attacking on another flank.Result: Irrelevance in the hottest sectors of computing.
Like I said, it's cinch up the belt time up in Oregon. Get tough or die. (As any kind of a trend maker in personal [post-PC] computing, at least.)
(RIM's in a big pickle too. They have no computing arm [like Apple and HP], no relevance on the web [like Google and MS], no native apps to speak of - and the BB phones and the new PlayBook have, I believe, very different code bases. Time for a Molson, ehh?)2.
If MS intends for this new codebase to be lean in any meaningful way and truly pointed at future devices rather than at past OS's and devices, they're gonna have a helluva' time doing that if they continue complete legacy support of multiple old versions of Win in deference to their huge installed corporate base (and their cheaper consumers) who hate having to change.
Any parts of that in the core, though, really have to go before they try to get it zip along on a Tegra chip.
So in many ways IMO the code will to be a fairly large break that's at least likely to make at least a big hunk of software and maybe all drivers that currently work on Win 7 and Vista (and often, still, XP) incompatible. And create a kernel (if that's the lowest level of an OS that directly faces hardware, excuse my ignorance if it isn't) which will support multiple processor families equally (something they tried but never really achieved with NT on the DEC Alpha chip in the mid-90's).
Not as big a break as OS9 with OS X and not as huge as Apple's whole shift to X86 from PPC, but in some ways, a bit of both combined. And a big challenge to an elephant that hasn't tap-danced well in a long time.
One possible approach might be to mostly virtualize Win 7 and Vista in ways that lets older programs operate mostly in a sandbox - on the level of Win 8 only (not Win Tab 8 or Win Phone 8). And/or to provide ISV's and peripheral makers tons of support to make their code and drivers functional on Win 8. In kind of a combo Cocoa/Carbon, Rosetta and/or Parallels Coherence way. Or something like that.
That might tide them over until native W8 programs come along. And MS does know a thing or two about virtualization.
Finally, it also means partially rearchitecting all of their own own PC and Server programs over a relatively short period. And they gotta lotta programs.
And that's a pretty challenging To-Do list. For something that might be too late to matter enough in the first place.
Man, how the shoe's moved to the other foot! Now all the pressure's on the one time school bully who's looking more and more like Mickey Rourke's face in The Wrestler. MS is getting beaten up by multiple opponents and they're wobbly on their feet.
So are they gonna suck it up off the mat or are they goin' down??