Linked by Adam S on Thu 10th Jul 2008 16:58 UTC
Windows Gadgetzone.com has an interesting artcile on 20 things Windows 7 MUST include (their emphasis, not mine). They begin "Despite its enhanced security, improved CPU scheduler and excellent stability, it's still the flawed gem in many critics' eyes. But can Microsoft win back the XP crowd with its upcoming Windows 7 offering? The fact is, they have to." My Take: Not sure I agree with them all -- do home users really care about WinFS? -- but some, like home user licensing and simpler management of startup items would be really compelling features for upgraders.
Thread beginning with comment 322379
To read all comments associated with this story, please click here.
20 things they must do
by robertojdohnert on Thu 10th Jul 2008 19:09 UTC
robertojdohnert
Member since:
2005-07-12

Interesting but not all are feasible. Considering 32bit is still the lead selling chip and continues to be and probably will be when Windows 7 is released, making it 64bit only will only hamper Microsofts ability to push Windows 7. The world will make the transition but doing it now wont help Microsoft or even the Linux guys. Also do some research WinFS is not a NTFS replacement, it was a relational database. I say WAS because WinFS is dead.

Reply Score: -1

RE: 20 things they must do
by fretinator on Thu 10th Jul 2008 19:15 in reply to "20 things they must do"
fretinator Member since:
2005-07-06

Considering 32bit is still the lead selling chip and continues to be and probably will be when Windows 7 is released


Say what? As far as I know, almost all computers are now sold with 64-bit processors - either the Intel Core2 Duo or the AMD Athlon/Turion X2 (or even Quads!). Only a tiny handful come with mobile Celerons or similar class models. Just because most of these computers are sold with 32-bit Vista, that does not mean the processor is 32-bit. I think the vendors shy away from 64-bit due to driver and software compatibilty issues.

Reply Parent Score: 3

RE: 20 things they must do
by atsureki on Thu 10th Jul 2008 23:15 in reply to "20 things they must do"
atsureki Member since:
2006-03-12

Interesting but not all are feasible. Considering 32bit is still the lead selling chip and continues to be and probably will be when Windows 7 is released, making it 64bit only will only hamper Microsofts ability to push Windows 7. The world will make the transition but doing it now wont help Microsoft or even the Linux guys.


The other reply is correct. If you're talking about x86 home computers, 32-bit chips are essentially out of the market.

Indeed it won't help Microsoft, as compatibility, especially of the backwards variety, is what sells their software, so in fact it might help Linux.

Also do some research WinFS is not a NTFS replacement, it was a relational database. I say WAS because WinFS is dead.


Relational databases already exist, as they did when WinFS was announced. WinFS was going to be a relational database filesystem stored as XML. That idea turned out to be as absurd as it sounds, and Microsoft's first response to its failure to come together and perform within reason was to reduce the scope of their goals for it, which is probably where you got the idea that the FS in WinFS stands for something other than FS. But you are right about one thing: WinFS is dead.

Reply Parent Score: 1

PlatformAgnostic Member since:
2006-01-02

WinFS used SQL as its backend, not XML.

The project was essentially a research incubation that got picked up by some windows execs much to the chagrin of the folks actually producing it. The technologies behind WinFS got distributed in various ways, including into FeedSync and ADO.NET, so it's not like WinFS failed to produce anything.

Reply Parent Score: 3