Microsoft's flagship software, Windows, built upon the same core architecture as preceding versions, seems to move an inch when its competitors take a lap.
(From The New York Times)
The story "Windows could use a rush of fresh air" published June 28, 2008 at 3:44 PM is no longer available on CNET News.
Content from The New York Times expires after 7 days.






Stand by for a re-tread of Vista in Windows 7. Their only hope will be that they slim down the number of pre-loaded services enough to make it quick, and spend the next year-and-a-half stream lining the processes they need to have loaded to run well (as well as get rid of some UI bloat and annoyances). They will then have a "respectable" product, but still not the one they need to move into the future with the flexibility in code design that the *nix's do.
Microsoft can't start over. They've forgotten how. More importantly, they are unwilling to shoot application compatibility in the head, even when it's critical to do so, and when a freebie of XP running under a VM (heck - they OWN a virtualization technology) would suffice, and would let them truly start over again. Windows 7 is truly Windows Vista warmed over. Perhaps it will be better. But at it's heart, it will still be Vista, and Microsoft will have to market the bejeezus out of that release to get people to mentally separate it from Windows Vista.
I'm betting, if Microsoft did what you suggest, they would have five years to catch up with the current security and compatibility level. By then, fifty percent of their user base, that otherwise would have stayed wth Windows, would have moved to other platforms. Does that make business sense?
Sell Both. XT/Vista/7 but stop with 7.
Sell 8 which is the new from ground up. If folks want to stick wtih 7. Great. If they want to move to 8. Great. 7 becomes the legacy OS. Nothing new is released. They just sell it and ride the cash cow.
You seem to be making a lot of strong, but extremely vague assertions
1. Your multi-platform app may show slower benchmarks, but thats pretty anecdotal. Was your program just a quick and dirty port? How many resources were made available to properly optimize your program for the Mac? Is your Mac port a Cocoa port? Carbon? Java? Or something else like Adobe AIR even?
2. What do you mean that OS X [UI] is only a single-threaded mishmash?
According to Leopards Developer overview page:
"Mac OS X is built around a powerful, integrated stack of graphics technologies, including OpenGL, Core Animation, and Core Image. These provide a solid foundation for application developers to create great applications. Mac OS X's multithreaded graphics layer handles application windowing, 2D and 3D drawing, animation, and multimedia."
3. I would also have to disagree that major OS X versions are "pretty thin", this sounds more like uninformed Windows fanboy talk than a OS X developer speaking. Every major version so far has provided many consumer visible features as well as many developer features, Leopard alone for developers brought:
-New Versions of Xcode, and IB.
-Instruments app for performance testing and optimization
-Objective-C 2.0 and Garbage Collection
-Core Animation
-Updates to Core Data
-New NSOperation API for improved multithreading
-Lots of 64-Bit improvements for Cocoa
-and a lot more stuff to make developers lives easier and other stuff to play around with.
I would also say it's incorrect to say that Snow Leopard "fixing" internals. Apple deserves a lot of credit for making a release thats more engineer focused than marketing focused.
4. Also regarding burning developers on the 64-bit transition I'm guessing you're talking about Apple dropping 64-bit support for Carbon?
I guess if you've got a lot invested in it(seems like only MS and Adobe are the main ones anymore though) then it sucks, but Apple has been saying for Years to get off the carbon train. It would suck to be one of those developers and have to do all the work to transition to Cocoa, but in the end having Apple focus solely on Cocoa will be better for all OS X developers as a whole.
Does staying in a lifeboat with a big hole in the middle make sense when everyone else around you is moving to higher ground?
Also, 'When Apple ditched it's codebase in favor of a new one... their user base was composed mainly of early adopters not caring much about compatibility...' Are you kidding? At the time, the user base was mainly publishing houses, advertising agencies, recording studios etc. who care about nothing but maintaining their existing processes. It was not an easy transition.
Lastly, that boatload of applications you claim to 'care about', how many of those do you use on a daily basis? 10? How many of those are already cross platform? How many started on the Mac in the first place? Photoshop etc.?
Beg to differ. Apple customers always cared about compatibility, but only compatibility that makes sense. That's the key difference between Microsoft's approach to backwards compatibility and Apple's approach. Microsoft points to that arcane DOS program and says, "Wow, look, it still runs under XP or Vista!"
Mac OS X, up until Leopard, always had the ability to run Classic Mac programs. The compatibility layer that Apple developed was ingenious - basically, it was a built-in virtual machine that simulated a classic Mac. But instead of worrying about perfect compatibility, Apple focused on what was important and what was doable given their limited resources.
Turns out, by PRIORITIZING needs, Apple made the transition relatively painless. Sure, a minority of users ******* and whine because some obscure program didn't make the transition, just as a small tiny fraction still thinks Apple betrayed them by dropping Classic support in Leopard.
The thing is, Apple was willing to do what was right even when it made a small group of users angry because it advanced the platform by light years for everyone else. Jjust look at all the benefits Apple made when it switched from PowerPC to Intel - I doubt most people today even realize that Macs used to NOT run on Intel processor because the transition happened so seamlessly.
Could Microsoft successfully migrate Windows to a wholly different processor architecture while allowing 90% of existing apps to run unmodified?? Because that's essentially what Microsoft needs to do, and they don't even need to switch processors, but as the article noted, MS doesn't have the guts because it's afraid of pissing off the 1% of users who shake an angry stick at 99% compatibility.
Meanwhile, Apple has gained 3-4% marketshare while the house of Windows is burning down.
Apples has it easy. It is the only hardware manufacturer that needs to support it's own OS. And how many business and end-user applications does Apple have to support vs the number in Windows?
Windows is the OS that runs a lot of business-critical applications like POS, even ATMS, etc.
But as much as Microsoft would want to make radical changes to Windows, it has to do it in a very responsible way.
And vitaboy, so you think the switch from PowerPC to Intel is significant? Windows runs on Intel32, Intel x64, Itanium, AMD64, used to run on DEC Alpha. Moving from one processor family to another is "easy" compared to shifting to a code base that would have a radically different API. And wow, what an achievement, Apple has gained 4% marketshare (very good really since it nearly collapsed to 0% if not for a timely save by a 150M dollar Microsoft cash infusion into Apple.
So you see, it's not that easy...
Compatibility and the loyalty of its developers is what lead to Windows current market-share. I agree that it's also the very thing that "maybe" pulling itself down today. But I'm sure, Apple or any other OS vendor wouldn't mind to have that kind of problem.
Not true, Sun Microsystems as well as IBM and HP (among others) maintain support for their own operating systems for their own hardware product (hence: Solaris, HP-UX/OpenVMS and AIX).
"And vitaboy, so you think the switch from PowerPC to Intel is significant? Windows runs on Intel32, Intel x64, Itanium, AMD64, used to run on DEC Alpha."
You're forgetting that Mac OS X was originally NeXTstep, which supported multiple CPU platforms including Motorola 68k, Intel x86, Sun's SPARC and HP's PA-RISC; which when Apple acquired NeXT, they ported it over to IBM's PowerPC platform. So Apple is probably more experienced than even Microsoft at handling CPU migrations since they've done it multiple times over (68k -> PowerPC -> x86).
"And wow, what an achievement, Apple has gained 4% marketshare (very good really since it nearly collapsed to 0% if not for a timely save by a 150M dollar Microsoft cash infusion into Apple."
Apple is enjoying awesome Mac growth these days. They currently lead the PC industry in growth by nearly 3 times and this has been a positive upswing for 3 years now. If marketshare mattered all that much, Apple wouldn't worth 2-3 times more than Dell
Microsoft's $150 million dollar investment did not save Apple (Apple was a $2 billion dollar company at that time and Microsoft's donation was like a drop in the bucket). Apple has just acquired NeXT for around $420 million and Microsoft had to settle with Apple on various patent infringements regarding IP in Mac OS and Quicktime that was an undisclosed sum worth way more than the $150 million Microsoft invested in Apple. From what I read in Time Magazine's interview with Steve Jobs (a 1997 issue published after MacWorld Boston), the $150 million dollar investment was Bill Gate's idea that was a symbol of good faith that Microsoft was devoted to Microsoft Office for Mac and possibly to help influence Apple to change the Mac OS default web browser from Netscape Navigator to Internet Explorer (and IE for Mac OS was a better web browser than NN during that era). What you could say is that Microsoft helped save Apple from ill-relevance in the computer industry, which wasn't financially correlated.
"Compatibility and the loyalty of its developers is what lead to Windows current market-share."
That may be somewhat true, but Microsoft abusing its monopoly and holding a contractual noose around the necks of PC OEMs like Dell, Gateway and etc... surely had way more of an impact on Microsoft success than anything else.
Read the below article for more insight on Microsoft's stranglehold on the PC industry during the late 90s.
http://www.birdhouse.org/beos/byte/30-bootloader/
Any one with a business head would know. Apple is the king of marketing and when they get the content like the IPOD it's over.
I think that MS needs to remove all compatabity pre Windows 2000 and make it GUI more independable of tasks unlike Vista which can hang on GUI now. It would be nice to see them KILL Win32 as I use X64 only.
Last reason MS can't rewrite is the governments and lazy devs. Most devs wouldn't support it and MS can no longer create competing software.
The "ancient frame" your referring to is Windows ability to run on so many different types of hardware. It is also the ability to maintain an API for developers that slowly migrates across generations of technology(i.e. 16-bit, 32-bit, 64-bit, DOS, Windows, .NET. This is why Windows is running on most pc's in the world.
"Adding features, plugging security holes, fixing bugs, fixing the fixes that never worked properly"
Give me a break. What do you think all these Mac OS X releases are?
"foundation that was never intended to support such weight"
Again... what are you talking about? Even XP clearly supported the "weight" of doing so many things the MAC OS X will never do.
"Windows seems to move an inch for every time that Mac OS X or Linux laps it"
Suggesting Linux laps Windows is...rediculous. Yes, Mac has always led in the user inteface, but even this may be short lived. If you look under the covers of Vista you find a vector based graphics system that is hardware accelerated just as games are today. You can bet Windows 7 and all the application developers are going to learn alot and be able to deliver compelling user intefaces on top of that 3 yr. old ancient foundation called WPF.
Windows 7 refers to the major version number of windows. NT 4.0, Windows 2000 (ver. 5.0), XP (ver. 5.1) (Vista ver. 6.0). You can type "ver" at any command prompt to see this info.
The only thing I agree with in the article is the fact Windows does too much. However your suggested fix of "starting over" is wrong as others have pointed out. Take a look at Windows Server Core 2008 and you see they are already moving in this direction of delivering a more modular Windows.
It's always such a pain to have to configure new machines and remove the unnecessary (or security compromising) "always has been, and will be a part of Windows." Leave those stuff on a server at Microsoft that people can download if they need to, but deliver a slim basic install.
I don't see the point of MS prodding users to newer and newer versions of Windows. If someone wants to buy 98 SE, 2000, or XP, then let them instead of trying to twist their arm into buying something they don't want.
Case in point--Microsoft already has a stripped down version of Windows - Windows Fundamentals for Legacy Computers. But can most people buy it? No you can't because it is only available to enterprise subscribers of its software assurance program. Yet, this would have been the ideal version of XP to sell to users of older computers (you know, those still using Win 98 SE).
But because MS feels it has to respond to (choose one: Netscape, Yahoo, Google, Apple, etc.) it sells a default Windows install that is so stuffed with unwanted bits that compromise security and performance.
Gets your Windows group back into the OS business and out of the "platform for other stuff " business
Basically, that was the way DOS worked with command.com being the core and anything else being loaded as needed. The benefit is compactness and speed.
Speed and compactness are apparently what Apple is shooting for with next years Snow Leopard upgrade. The direction of the consumer market seems to be towards compactness (Think IPhone and IPod). A small, "'just enough' operating system" is perfect for that market. To be part of that market, and not just the business market, Windows has to go on a diet.
As a consumer my eyes simply see what's better, I don't need to understand any technical speak or explanations. One of the main reasons that I skipped Vista is because it's very slow and resource hungry, even on new computers. If Windows 7 is the same story, I won't say doom, but definitely more market share loss to OS X, Linux and whatever else is out there.
People are tried of bull.... no ******** please.
I find it funny how some of these same trolls that crap on Windows for bloat also crap on it for compatibility. You can't have it both ways. Their spin is always based on such double-speak.
Ya know, in 1983 I thought it would be cool to put the digital music from CD's onto solid-state storage that could be plugged into players. I should have patented that one...
- by Mr. Dee June 30, 2008 6:54 AM PDT
- I am sorry, but there is a lot of misinformation and bias in this article. Mac OS X's heritage upon which it is built is even older than NT itself. Development on NT started in late 88 when Microsoft hired Dave Cutler, so NT is probably one of the youngest Microkernels next to Linux which was developed around '91 by Torvald. There is also confusion between the code bases, Windows NT is completely different from Windows 9x/3x/1x. The only similarities they shared were version names and API's for those legacy applications you speak of. Microsoft does not need to rewrite Windows, they can clean it up, just like they did for example with the release Windows XP Professional x64 where they removed things like AppleTalk, POSIX compliance and NetBEUI. You must remainder just like Linux or Unix, NT was designed in mind to be a portable OS, in fact during its development it was specifically targeted at different platforms such as PowerPC, Alpha, MIPs, the Intel processor it targeted had to be emulated. So I would revise your analysis before dooming Windows. A lot of the work over years has been targeted at componentising much of Windows where vital components like the Network Stack, graphics don't create lots of dependencies. Rumors are much of the built apps for instance will be optional. Vista's only regret is, it made necessarily architectural for security and took a long time to reach market. Microsoft could even move legacy compatibility to a virtualized stack where old apps work normally on newer versions of Windows without a hitch.
- Like this Reply to this comment
-
Showing 1 of 2 pages (41 Comments)