A minor point, IIRC
<< > -*NIX file system was going to be supported.
NT based OSes have support for IFS (Installable File Systemss) so all that
would be needed is for someone to write a driver or module in support of
some other file system. But that begs the question: "Which *NIX filesystem?".
There are several to choose from, many still in beta stages of development.
And it was more likely that MS would write (in-house) an HPFS IFS driver than
one for ext2fs or any of its close companions. I'm guessing that no third-party
developer has tried to tackle it because the file system access has to also
be tied into the security model of the OS, which was still a moving target until
XP was released.
I can't speak for performance in comparison to Win2K, except to note that
it is supposed to be slower than Win98SE in some operations... XP to me seems
faster at file operations thru explorer than my W98SE install, but slower at
navigation and file operations thru the command line.
Think of .NET as a next-generation IIS... It is meant as a plug-in/add-on for
the server class OS, but provides services that cover Pro and Home versions as
well.
<<
To further confuse the issue expect to see just about everything coming out of MS called something.net for the next year or two >>
something.NET, something XP, and something 2002 (at least this year). Sometimes
with more than one together. By mid-summer we'll all have that .NET 2002 XPerience.
I'm sure what is being said here is echoed in part in
this thread
about what it would take to get people to switch to a Mac.
Insidious,
<<
To the "mainstream", giving them Linux is like giving them a car but not telling them it needs gas. >>
IMO, its more like giving them a manual transmission, when all they are used to
driving is automatics (and in some cases, automatics with overdrive).
The frustration is that some of it does work "out of the box", if you know how
to use a clutch... (they just don't explain the clutch part).