Longhorn
-
I don't get it. A few MS evangelists require NDA before they say anything regarding Microsoft next operating system, codenamed "Longhorn". Alternatively, they urge people to pay 2000$ for September's PDC. At the same time, core papers are publicly available. Here is an example about shading[^] text and images. The point is, who are they kidding?
-
I hope it ain't bollocks mate.
-
"The Windows Longhorn client platform uses Microsoft® DirectX® for all screen display" :omg:
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygenYeah. This is frightening when you know that most advancement since DirectX 3.0 is about 3D stuff. Imagine that to blit on squared surfaces, you have to create a D3D surface, load a texture, apply it using whatever application model, just to get the job done. I have personally given up all work (shareware progs) based on DirectX. None of these where working on someone else's machine!
-
Unless they totally replace dxt and GDI, they are forced to use GDI+. GDI+ is available today, and they can't break it that easy.
-
Unless they totally replace dxt and GDI, they are forced to use GDI+. GDI+ is available today, and they can't break it that easy.
What if they provide a emulation for old apps, the ones that were written for older os's, this release being more than three years away it , the processor speed would've approached closer to or more than 5GHz mark. It would be interesting to see if they do something like that. Cheers, Kannan
-
i'll just say graphics is very different. Man... this is so big, yet they didn't reveal anything in the conference link. get ready for a wild ride in october. this ain't kansas anymore, dorothy. Thanks, Wes
-
I am contracting for Microsoft right now. I am using both the next VS.NET Whidbey compiler and working with the next Longhorn OS. All I can say is that they both have really major stunning changes, especially Longhorn. You won't be able to tell from some of the alphas that leaked out. But in October's PDC, all will be revealed to the adventurous few who take off to PDC. It's significance will rival that of the June 2000 PDC that introduce VS.NET and C# and the CLR/.NET frameworks. Good things are going to happen to the .NET developers. The papers you see are from the WinHec conference. Hardware developers need more of a lead time than software developers. You ain't seen nothing yet. Thanks, Wes
Wesner Moise wrote: Good things are going to happen to the .NET developers. I agree with that comment. One of my close friend who is working at Microsoft on Longhorn project. He told me the same thing, BTW whatever he told me it's in the 'vault' ;)
"If a jug falls upon a stone, woe to the jug. If a stone falls upon a jug, woe to the jug. Always woe to the jug"." - KaЯl
This signature was created by "Code Project Quoter". -
I don't get it. A few MS evangelists require NDA before they say anything regarding Microsoft next operating system, codenamed "Longhorn". Alternatively, they urge people to pay 2000$ for September's PDC. At the same time, core papers are publicly available. Here is an example about shading[^] text and images. The point is, who are they kidding?
Yep - it's incredibly frustrating to not be able to talk about aspects of Whidbey, Longhorn and Yukon and then find pages and pages of stuff on topics you have just been expressely told not to discuss. cheers, Chris Maunder
-
Yeah. This is frightening when you know that most advancement since DirectX 3.0 is about 3D stuff. Imagine that to blit on squared surfaces, you have to create a D3D surface, load a texture, apply it using whatever application model, just to get the job done. I have personally given up all work (shareware progs) based on DirectX. None of these where working on someone else's machine!
Well, I'd expect MS to remain with the GDI/GDI+ interface for that - after all, it says "all drawing", not "all drawing of new programs"... (But with your attitude towards MS you'll be doubting that I guess ;) )
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen -
Yep - it's incredibly frustrating to not be able to talk about aspects of Whidbey, Longhorn and Yukon and then find pages and pages of stuff on topics you have just been expressely told not to discuss. cheers, Chris Maunder
Chris Maunder wrote: Yep - it's incredibly frustrating to not be able to talk about aspects of Whidbey, Longhorn and Yukon and then find pages and pages of stuff on topics you have just been expressely told not to discuss. I would assume they disclose more information to you than what is covered in the web pages online. Then again, I could always being assuming wrong, but how does an NDA restrict you from talking about something that is publicly available? -Nick Parker
-
Yep - it's incredibly frustrating to not be able to talk about aspects of Whidbey, Longhorn and Yukon and then find pages and pages of stuff on topics you have just been expressely told not to discuss. cheers, Chris Maunder
I am afraid the point about the NDA is not only to get you to shut up. The NDA also prevents you from selling a competitive product. It's my belief that everyone signing NDAs these days are screwed, especially if they are software companies competing in those spaces. For instance, in 98 I was working on video asset management software on personal projects (2 sharewares) and wanted to work in companies that were doing just that, video asset management products. The fact is, those companies got me to sign NDAs on recruitement interviews not only to get me shut up, but essentially PREVENTING me from releasing a product that would be compete with theirs (was in alpha). May be the generalization is wrong, but if anyone getting through the NDA process is getting screwed the way I have been a few years ago, then I recommend not to sign any NDA at all first, and leave the PDC where it is. In addition, so many people flocking there will of course result in mass conferences and, as I expect it, quite frustrating moments.
-
i'll just say graphics is very different. Man... this is so big, yet they didn't reveal anything in the conference link. get ready for a wild ride in october. this ain't kansas anymore, dorothy. Thanks, Wes
This is good and bad news. Good, I am fed up with the way Windows and controls are drawn. If all of this is changed, it also means that the CLR Winforms will also drastically change since today it hardcodes WIN32 plumbing. The OS will have to come with another .NET major run-time. Bad, applications will have to be written for that OS, and won't work on others. If that is true, don't expect corporate people to switch to it. There could be an emulator sold along, but... Longhorn is not an OS, it's a whole new PC : - new and breaking hardware (NGSCB chip, new display cards, ...) - new and breaking OS - new and breaking .NET run-time - new and breaking compilers and dev tools - new and breaking apps