Slashdot Mirror
Microsoft Ponders Windows Successor
InfoWorldMike writes "Before Vista is even out of the gates, a Microsoft exec was talking Wednesday about Windows' replacement at a VC conference. Speaking at The Venture Forum conference, Microsoft's Bryan Barnett, a program manager for external research programs in the Microsoft Research group, said multicore architectures are of particular interest when weighing what to put in future operating systems at the company. "Taking full advantage of the processing power that those multicore architectures potentially make available requires operating systems and development tools that don't exist largely today," Barnett said. Well, with Vista in the pipeline as long as it has been, you must admit it is not surprising Microsoft is taking the long-term view. And it won't be built overnight: There is no timetable for a Windows successor right now. But early work on this effort has not yet been organized, with five or six small projects afoot in various places throughout the company, Barnett said."
Yeah, you know what would be *funny*? If Microsoft licensed OS X.......
:-)
No, seriously..... OS X runs on Intel now, and Apple is working hard on compatibility layers for multiple OSs and it is the slickest, most stable, most beautiful mainstream OS out there right now. It would be especially funny as back some years under Gil Amelio, Apple actually looked at licensing Win NT for the new OS when Copeland was in horrible shape. Thank gawd that never happened or Apple would be where SGI is now (or worse).
Hey, you know that Microsoft has used Apple as their R&D arm for years now, right? Why not just formalize it?
In all fairness, I am not saying that Microsoft can't do it themselves, I'd just like to see a return to the good 'ol days when Microsoft made good, solid applications and were not trying to be all things to all people. They used to you know...... I am thinking of the early versions of Excel (Multiplan) and Word on the first Macintoshes along with Microsoft MacEnhancer, Chart and Basic.
Although one has to wonder what is going on when Microsoft's programmer team for Windows is in the several-thousands and Apple's development team for OS X is around 300.
Visit Jonesblog and say hello.
What I think is odd about this is that the NT architecture has never really even been fully utilized, at least on the consumer side of Windows. In a lot of respects, NT is a pretty clever system, including highly individualizable security for files, processes, etc. It also supports multiprocessing well, contrary to the implication of the article. Point being, I'm not so sure the solution for Microsoft is to throw out NT and move on to something else (Singularity, or whatever it may be). I would suggest they instead look at the features already in place with NT and look at ways to actually enable and present them in a reasonable way in their consumer OSes. I guess this is the plan in Vista, but we'll see. The other thing I'd like to see Microsoft do is separate out the kernel-level framework (NT system, drivers, etc) from the UI framework, so that it would then be possible to treat those two elements separately, in the same way that Linux has the kernel and X/Window Manager stuff totally separated out. But, I guess that would make it harder for them to make money, so it's unlikely.
Free Conference Call -- No Spam, High Quality
"Taking full advantage of the processing power that those multicore architectures potentially make available requires operating systems and development tools that don't exist largely today," Barnett said.
Maybe MS should pay attention to the fact that they have never taken full advantage of any processor's power. Most products they have put out these days just hog system resources, forcing systems to have more powerful processors, more RAM, etc. without ever really harnessing their power. The increase in power is just to make it seem like the bloat-ware is running better than it actually is.
Support a true independent artist - Leila Lopez
I actually find this really interesting. Not that Microsoft is talking about a new OS after Vista, but that they're talking about it being a successor to Windows, not a new version of Windows.
.Net runtime whatchamajigger, so new .Net apps will run seamlessly on either Windows XP, Windows Vista, or the new OS. Then they'll hack VirtualPC to make a stripped-down XP or Vista run transparently in the background, and run old applications inside of that (and new hardware will be fast enough that performance won't be a problem). It's basically the same idea that Apple did five years ago with Classic, the Mac OS 9 emulator that runs on Mac OS X. Chances are, just like Apple modified the Mac OS Toolbox, named it Carbon, implemented Carbon in the new OS and added the CarbonLib library to the old OS so Carbon apps could (sort of, in theory) run on both platforms with no modifications (it didn't actually work that well, but it did make it possible to port existing apps without rewriting the whole thing), Microsoft will probably come up with a derivative of Win32 that apps can be ported to that will run on the new OS. Meanwhile, they'll move as much as they can over to .Net.
.Net and emulate Windows, then they'll have the flexibility to move to a different processor architecture if they want, without the compatibility problems that Apple is going through with that.
Microsoft has been trying to dig themselves out of the hole that they dug themselves into for several years now, and they can't do it (i.e. fix Windows) without breaking backwards compatibility with old applications, and as long as they keep releasing new versions of Windows, they have to maintain that backwards compatibility, or word will spread quickly and people won't buy it. Besides, if you have to buy new applications when you buy your new PC with the new OS, why not buy the Mac version of those apps instead, and switch?
But then Microsoft bought VirtualPC, and a solution began to unfold. If they release a new OS, and don't call it Windows, then they don't have to maintain backwards compatibility with existing Win32 applications in the OS. They'll port the
And hey, if they move what they can to
Flame on!
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
Thanks for your excellent response. Valid or not, here's why, to me, XP feels like DOS:
1. There are files everywhere in a root drive called C:\.
2. When my computer boots I see all these grey characters, bios, IDE info, etc. etc.
3. Some applications, when installed, seem to be "everywhere"... they aren't just single little entities.
4. There are thousands upon thousands of files, where you don't know what they do.
Of course, Windows has a lot of plusses -- I can't remember any time Windows XP told me I didn't have enough conventional memory. And these problems are not unique to Windows, either.
But I think my original point is that we would have to start seeing durastic changes in the way the computer works for the "next gen" operating system. Vista, IMHO, does not cut it.... in fact, it is (at least from what I have seen in the beta) the worst OS to be released since Windows 98.
You know, I remember testing "Windows NT 5.0 Beta 2", and the desktop could barely draw itself, there were loads of icons missing, you couldn't run MS Office, the admin tools would bluescreen the box, and it took about 30 seconds to open the start menu. And I was thinking "They spent 4 years building THIS?" And that turned out to be Windows 2000, widely considered to be the least crap version of Windows ever.
There's the real possiblity that Vista might turn out to be a unusable crap heap, but its way to early to make that call. I'm kinda suprised that they had a public beta with 6 months (plus 3 more once it gets pushed again) to go.
Whenever I hear the word 'Innovation', I reach for my pistol.
At the OS level, a decent scheduler and not using giant locking will get you most of the way.
= 13736089
To get the most out of it though, the applications need to be multi-threaded and multi-threaded programming in (standard) C/C++ is not straight forward, in fact it can be almost downright impossible to debug.
Other programming languages are much more suited to multi threaded programming, particularly those that use the CSP model.
Construction of Concurrent Systems Software
http://www.herpolhode.com/rob/lec1.pdf
http://www.herpolhode.com/rob/lec3.pdf
http://www.herpolhode.com/rob/lec5.pdf
My favourite, of course, is Limbo but I only know of one environment where that is implemented : Inferno
here's another discussion on a similar theme
http://it.slashdot.org/comments.pl?sid=164547&cid
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter