|
|
User Controls
|
New User
|
Login
|
Edit/View My Profile
|
|
|
|
ActiveMac
|
Articles
|
Forums
|
Links
|
News
|
News Search
|
Reviews
|
|
|
|
News Centers
|
Windows/Microsoft
|
DVD
|
ActiveHardware
|
Xbox
|
MaINTosh
|
News Search
|
|
|
|
ANet Chats
|
The Lobby
|
Special Events Room
|
Developer's Lounge
|
XBox Chat
|
|
|
|
FAQ's
|
Windows 98/98 SE
|
Windows 2000
|
Windows Me
|
Windows "Whistler" XP
|
Windows CE
|
Internet Explorer 6
|
Internet Explorer 5
|
Xbox
|
DirectX
|
DVD's
|
|
|
|
TopTechTips
|
Registry Tips
|
Windows 95/98
|
Windows 2000
|
Internet Explorer 4
|
Internet Explorer 5
|
Windows NT Tips
|
Program Tips
|
Easter Eggs
|
Hardware
|
DVD
|
|
|
|
Latest Reviews
|
Applications
|
Microsoft Windows XP Professional
|
Norton SystemWorks 2002
|
|
Hardware
|
Intel Personal Audio Player
3000
|
Microsoft Wireless IntelliMouse
Explorer
|
|
|
|
Site News/Info
|
About This Site
|
Affiliates
|
ANet Forums
|
Contact Us
|
Default Home Page
|
Link To Us
|
Links
|
Member Pages
|
Site Search
|
Awards
|
|
|
|
Credits
©1997/2004, Active Network. All
Rights Reserved.
Layout & Design by
Designer Dream. Content
written by the Active Network team. Please click
here for full terms of
use and restrictions or read our
Privacy Statement.
|
|
|
|
|
|
|
|
Time:
13:32 EST/18:32 GMT | News Source:
Microsoft Watch |
Posted By: Robert Stein |
According to developer sources, Microsoft is cutting back Longhorn client's planned feature set so as to be able to make its current delivery targets: Beta 1 by next year and final release some time in 2006.
Microsoft is expected to announce officially later on Friday its future roadmap for the desktop version of Longhorn. And while developers and customers who expected they'd be required to rewrite their applications to take advantage of Longhorn may be happy with Microsoft's roadmap changes, others who were banking on promised Longhorn features, such as the next-gen Windows File System, will be far less so.
|
|
#1 By
3339 (64.160.58.135)
at
8/27/2004 4:22:58 PM
|
How often do you delude yourself, bob_c_b, into believing the rosiest of scenarios for Microsoft? I would bet that MW has been more accurate with their announcements than Microsoft has.
And, yes, by the way, Allchin has said it himself, and every major market is covering the story now.
This post was edited by sodajerk on Friday, August 27, 2004 at 16:31.
|
#2 By
7754 (216.160.8.41)
at
8/27/2004 5:06:13 PM
|
A bit of a disappointment. I wonder what will happen to the core of Longhorn, which was supposed to have a new driver model, etc.:
(from cNet:) "The code base for Longhorn will be the same as Microsoft is using for the Service Pack 1 release of Windows Server 2003..."
Not long ago, Allchin was showing a build of Longhorn running several video windows at once and then XP choking under the same amount--I wonder if that is something else that will be cut. And what about the improvements to the audio subsystem?
|
#3 By
17996 (66.191.120.226)
at
8/27/2004 7:49:45 PM
|
After reading several news stories, one may wonder:
With them releasing Avalon and Indigo to XP/2003 systems, what would be the reason for one to upgrade to Longhorn rather than just get these two components installed on their machine?
Well, Indigo we knew was going to be available separately. However, making Avalon available separately is kind of interesting.... The PDC 2003 version of Longhorn included an early version of Avalon that was NOT built on DirectX and did not include the Desktop Composition Engine. I would expect that they WILL keep the new driver model, DCE, etc. only available in Longhorn. Thus, Avalon on Longhorn will use 3D hardware and performance should be good. Avalon on XP, however, will be built on top of today's driver model and GDI foundation, and performance will not be that great.
The important thing is that the programming model for both (WinFX) will be the same, so that you can develop apps for Longhorn that still work on older versions.
#5, Regarding the code base being "the same" as Windows 2003 SP1... You can never believe the things you read on CNet/ZDNet. Basically, what happened was this:
First, open up this diagram from Paul Thurrott's site: http://www.winsupersite.com/images/reviews/windows_dev_trunk.gif
Once Windows Server 2003 (NT 5.2) RTM'd, they "froze" the NT 5.2 code base and the "main" code base became Longhorn (NT 6.0). As the diagram shows, Windows 2003 SP1 is being built on top the RTM'd Server 2003, in a separate branch. Meanwhile, though, Longhorn development has been happening in the main code base.
What happened was, so many changes were added to XPSP2 (and to 2003 SP1 in parallel), that they would then have to go and add these all into the main code base (Longhorn). Now, they've decided to axe the "main code base" and build Longhorn off of the 2003 SP1 codebase. Thus, after 2003 SP1 RTMs, the 2003 code base will branch off again, and the main code base will continue where 2003 SP1 left off.
|
#4 By
3339 (64.160.58.135)
at
8/27/2004 11:30:47 PM
|
Bob, AS I SAID, I would bet that Microsoft Watch is batting a better average than every stupid announcement out of Microsoft. And, of course, a dickrider like yourself, will say Microsoft is just providing guidance to developers. Well... remember Blackcomb was supposed to be out in 2004/2005. Now... we are getting XPSP2 with some frankenstein features cobbled on in 2006. Great.
Also, I would point out this cute little statement from Billy G himself:
"And we never had, in the Longhorn plan, WinFS server support. We were clear about that going back all the way to the PDC."
Hmm.. when MSWatch said exactly that every softy and his mother came out saying "BULLSH1T!"... Hell, even MS employees were saying MSWatch was full of sh!t... Now Billy G is saying just that, when it's convenient (i.e. they definitely aren't delivering it anyway). But of course, this should have been perfectly apparent to everyone at the PDC, right? Right.
This post was edited by sodajerk on Friday, August 27, 2004 at 23:32.
|
#5 By
23275 (68.17.42.38)
at
8/28/2004 11:54:42 AM
|
#16 Dead on!
I've tried to participate, more as an experiment, to see if some professional work could be enhanced within such forums, but it is impossible. It seems, and it's totally fine, that such forums are more for entertainment [of some sort], than anything of substance.
The MSDN world and others are productive, but a little less practical from a business perspective, and even MS Community favs like Neowin, which have some traction, but they don't contain much beyond one-liners that have little practical relevance.
The pieces they are based upon are little better.
For example, and I mean "geeze" WinFS is NOT/NOT a freaking file system and NOT/NOT and NEVER/NEVER was intended for Longhorn in the same way it was intended for Blackcombe!
The file search and access system in Longhorn will be as rich as always intended - just the API's and Platform components will not be delivered in it until Blackcombe - where it will be
available and included. It is about the smartest dern thing MS has done in a long time - gives devs Indigo now and preserves all that the new client was meant to be - while not delaying it with features that canot be broadly used until its server comes out. Gawd, please read what is written and try to "get it."
"That is my last post here at ActiveWin."
Oh well...back to work...good luck ActiveWin...best to all.
|
#6 By
3339 (64.160.58.135)
at
8/30/2004 7:33:48 PM
|
What's so "gay" about being a dickrider? I've got to teach you all a little slang.
|
|
|
|
|