After Vista
-
-
Quite possibly the codename for the next version of Windows is 'Vienna'. Since absolutely nothing has been announced it's pretty irrelevant. As for 128-bitness - there are no 128-bit general-purpose processors and I think it's pretty unlikely that there will be any time in the near future. Most computations are fine with a range of 32 bits. The main reason for going to 64-bit is the additional memory addressing capability. In theory that gives 16 exabytes (16 million terabytes) of address space. In practice only 48 bits of virtual address space are currently implemented, giving 256 TB of virtual addressing capability in total. If I recall correctly, this is currently further limited by Windows x64 editions to 16 TB of user-mode virtual address space. On the physical side, the processor implements 36 bits of physical memory addressing, which gives a total memory size of 64GB (at least on current Intel processors).
Stability. What an interesting concept. -- Chris Maunder
-
Not to be mean or anything, but I've been hit with new Microsoft technologies repeatedly all year and I'm a little jaded. All the new .Net 3 stuff, the Vista APIs like power management and system recovery, the new MOSS, the OpenXML format, Expression, Orcas, Linq, ... It's exciting stuff. But it would be nice if Microsoft would fix the problems they have now for a change. Like why is VS2005 so friggin slow and memory heavy? Why is Windows Media Player 11 unable to play videos smoothly on my laptop while 10 could do it no problem? Why do you have to forgo the nice WYSIWYG user controls designer in order to make SharePoint web parts that really use SharePoint? And, for the love of dog, why has no one put a button in VS that allows you to collapse all the projects in your source tree?
-
Not to be mean or anything, but I've been hit with new Microsoft technologies repeatedly all year and I'm a little jaded. All the new .Net 3 stuff, the Vista APIs like power management and system recovery, the new MOSS, the OpenXML format, Expression, Orcas, Linq, ... It's exciting stuff. But it would be nice if Microsoft would fix the problems they have now for a change. Like why is VS2005 so friggin slow and memory heavy? Why is Windows Media Player 11 unable to play videos smoothly on my laptop while 10 could do it no problem? Why do you have to forgo the nice WYSIWYG user controls designer in order to make SharePoint web parts that really use SharePoint? And, for the love of dog, why has no one put a button in VS that allows you to collapse all the projects in your source tree?
Dustin Metzgar wrote:
Why...
Because you make more money selling a new version of something than you do putting out a free service pack, of course.
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
Dustin Metzgar wrote:
Why...
Because you make more money selling a new version of something than you do putting out a free service pack, of course.
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
Maybe if they fixed it in the next version, I'd be fine. But SharePoint development is still done on an HTML stream and people have been complaining about the collapse all projects since the first Visual Studio .Net.
-
The more things change, the more they get worse.