Linked by Eugenia Loli on Wed 16th Nov 2005 01:53 UTC
Windows Microsoft announces that the next version of Exchange, its upcoming Windows Server "Longhorn" SBS and its Centro infrastructure solution for midsize businesses will only be released as 64-bit.
Permalink for comment 61268
To read all comments associated with this story, please click here.
Member since:


The extra registers can cause a small performance increase (between 0% and 15%) but won't make software more flexible. DEP or NX can theoretically improve security, but I've never had a problem that it would have prevented despite running Win95 and Win98 for ten years without anti-virus or firewall software.

3 GB of RAM might be common on desktop machines in 5 to 10 years, but a 32 bit CPU can handle up to 16 GB of RAM using PAE or PSE (36 bit physical addressing). I'd be very surprised if desktop machines need more than 16 GB of RAM in the next 10 years (despite the hardware requirements I saw for Vista :-).


For well written/portable software, the "long implementation cycle" means recompiling it. This has already been seen with GNU/Linux software. IMHO there are some situations where 64 bit is currently beneficial (large servers, specialized applications, etc), so the long implementation cycle could begin with these areas so that compilers, etc are ready well before desktop machines need 64 bit.


Very large databases and video editing are specialized areas that a normal desktop computer user is unlikely to worry about. Despite this, if a single application needs more than 3 GB of virtual memory it can be split into several processes - for e.g. 4 processes at 3 GB each (which helps for multi-CPU or dual core, and in some cases allows those processes to be run on different computers). For an example of this have a look at how Google works. I also seem to recall an article on OSNews a month or so ago about setting up a distributed rendering farm (but normal video editing wouldn't require that sort of thing).

Reply Parent Score: 1