 |
 |
| ActiveWin | Anonymous | Create a User | Reviews | News | Forums | Advertise | VBA in Excel | Users Online: 0 |
|
|
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
Active Network |
|
ActiveMac |
|
ActiveWin |
|
ActiveXbox |
|
DirectX |
|
Downloads |
|
FAQs |
|
Interviews |
|
MS Games & Hardware |
|
Reviews |
|
Rocky Bytes |
|
Support Center |
|
TopTechTips |
|
Windows 2000 |
|
Windows Me |
|
Windows Server 2003 |
|
Windows Vista |
|
Windows XP |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
Apple/Mac |
|
Xbox/Xbox 360 |
|
News Search |
|
XML/RSS Newsfeeds |
|
Pocket PC Site |
|
|
|
|
|
|
|
FAQ's |
|
Windows Vista |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows Server 2003 |
|
Windows XP |
|
Windows 7 |
|
Windows 8 |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox 360 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
Latest Reviews |
|
Xbox/Games |
|
Fable 2 |
|
|
|
Applications |
|
Windows Server 2008 R2 |
|
Windows 7 |
|
Adobe CS5 Master Collection |
|
|
|
Hardware |
|
Microsoft Express Mouse |
|
|
|
|
|
|
|
Latest Interviews |
|
Mike Swanson |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Advertise |
|
Affiliates |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
 |
Time waits for no one, not even Microsoft | |
|
||
| Time: 09:24 EST/14:24 GMT | News Source: ZDNet | Posted By: Byron Hinson | ||
|
Microsoft sees its near-term future as a series of "waves" of software that are key to its growth over the next couple of years. But with those waves slow to reach shore, the company--and its customers--may feel like they're caught in a riptide. For months, Microsoft has talked about a "Yukon" wave of products that would hit this year and a "Longhorn" wave that would follow a year or two later. The first wave is tied to the next version of SQL Server, known as Yukon, as well as to updated developer tools, known as Whidbey. |
||
|
Read Only Comments Return to News |
Displaying Comments 1 through 6 of 6 |
This is an archived static copy of ActiveWin.com. |
| #1 By 3339 (64.160.58.135) at Monday, March 15, 2004 11:48:56 AM |
|
I believe that's part of the point, becker.
Microsoft is talking up Longhorn despite it's never-approaching future release... Microsoft wants to play it both ways... Promise stuff now that they have no idea if they can deliver even in 3 years from now. "Programmers were told at last October's professional developer conference to start working on Longhorn, though the company now offers no timetable of when the OS might ship." Why should Microsoft be able to talk up the benefits of Longhorn and to encourage migration to Longhorn-specific technology when they can't tell us when they are going to deliver? |
| #2 By 2960 (156.80.64.137) at Monday, March 15, 2004 01:14:23 PM |
|
This whole Longhorn fiasco reminds me of Apple's 'original' System 8.0 (NuKernel) Operating System plans.
After severl years of waiting for the alpha, one year at the Developers conference, on the first day when everyone was fully expecting the developer beta CD's, Apple announced that the entire project had bee scrapped and said "we'll let you know our plans a little later". It took about 5 years, but we finally got there :) TL |
| #3 By 3339 (64.160.58.135) at Monday, March 15, 2004 01:31:33 PM |
| "little more than OpenStep 5.0/Mach" plus 4 years of developing Cocoa (OpenStep) plus the old MacToolbox with many new APIs (Carbon) plus Java plus QuickTime plus OpenGL plus Quartz Extreme plus many other Core systems (Core Audio, ColorSync and many other classic MacOS APIs and others intended for Copland) plus the cold and dead MacOS of yore (Classic) plus.... wait, aren't we talking about Longhorn? |
| #4 By 135 (208.186.90.168) at Monday, March 15, 2004 02:15:06 PM |
|
Hey, if you're looking for a date I suggest you try match.com.
|
| #5 By 931 (66.180.122.62) at Monday, March 15, 2004 05:31:52 PM |
|
actually it rather reminds me of all the Cairo babble back in the mid ninties.
Yes we ultimately got Cairo (ala win2k in december 1999) but it was basicly 2-3 years late based on original timelines. |
| #6 By 2459 (24.175.141.98) at Monday, March 15, 2004 08:19:57 PM |
|
Why should Microsoft be able to talk up the benefits of Longhorn and to encourage migration to Longhorn-specific technology when they can't tell us when they are going to deliver?
Because it clues developers in on what's coming next, and because there's actual code to develop against. Longhorn and Whidbey alphas were released during the PDC. Yukon is currently at beta 1 (beta 2 is a few months away). Whidbey is supposed to start trickling further builds out to MSDN on a frequent basis in a few weeks. Longhorn will have a refresh build, then beta sometime around this summer. Though some of the APIs will change from the current build up to Beta, developers can at least experiment with the platform and plan out how their applications will integrate with the platform. Hardware developers can test the new driver models and plan new devices. If MS didn't give advanced notice, you'd have more ISVs/IHVs with incompatable products than you do now. It's bad enough when certain companies know a product is at Beta 3 or RC stage, and they don't start testing compatable drivers or a software update until a few months after RTM (if ever). Additionally, the major thing that was reiterated at PDC and in other presentations wasn't that developers should start making the next version of their applications Longhorn-specific. It was that they should move to managed code and (preferably) build for the Limited user account. This would strengthen the security of their apps, possibly increase productivity, and prepare them for the move to Longhorn at a later date. By moving to managed code, not only could they target current platforms, but they could run their apps in Longhorn with few or no changes. Plus, it'd make it easier to add Longhorn-specific features if/when they choose to do so. |
