Where can I get the full, unwatermarked, high-res, quality image of the blue desktop pic in some of the Longhorn screenshots? That's prob. my favorite part of them.
Now, let's say that the complete Longhorn package, with all the extra, takes up a small fraction of the 1TB that's been posted, say, 10GB (wild impliciation). (I'm pulling 10GB out of the 1TB to demonstrate a point, so Longhorn does not take up 10GB of Hard Drive space unless there's otherwise proof of it.) I see two immediate issues:
(1) You know how much debugging it would take Microsoft coders to fix a problem that they can't find so easily? They (eventually) find the problem, recompile the 10GB OS, and test it again. That takes a while. Not to mention, what's going to be in the 10GB? Code? Because if the percentage of the 2GB that took up Hard Drive space on PCs for XP is the same as that for PC Hard Drives for Longhorn, then it's going to take so much longer to write the code, debug, add features, retest the complex GUI, and make sure that with all the complexity involved in the 10GB of GUI code that Longhorn operates as expected.
- Programming issues
(2) Even IF the package was 10GB, how much "dinero" ($$$) is Microsoft going to ask for? Better yet, what is Longhorn Server going to cost? If Windows Server 2003 cost max. $4000 initially, what's Longhorn Server going to cost, with all its high-end props, 3D interface, and needlessly complex coding that is difficult to debug? $6000???? You might as well buy a mini-1TB server using that cash and today's technology.
- Cost
I'm still waiting to find out what the 3D interface is supposed to do actually. Like, for the 3D GUI for Longhorn, can Longhorn be managed easily, not require over-the-top specifications, and, most importantly, have its 3D engine overall outperform two-dimensional operations for things like file navigation, internet browsing, email, text, image/video editing, and the like? If Microsoft can pull that off, then that'll be amazing.