A Quick Look at Longhorn Build 4053

An anonymous reader writes "Even though the next generation Windows product is not due until late 2005 or even 2006, here is a look at what Microsoft has in store for it's future operating system. 'Without a vast amount of tweaking, this build is a resource hog. At idle, with no applications running, the commit charge is at a whopping 483 MB!! Obviously, the final release or even the beta releases will not consume this much of the system resources.'"

Comments

Compile modules?

[TobiasSodergren]

It's maybe possible to save ram by compiling stuff you don't need as modules, like:

* IE
* The clipper thingie in office
* The animated, fading menues from the start button

And other stuff which obviously live in the kernel :)

Not obvious!

[www.sorehands.com]

"Obviously, the final release or even the beta releases will not consume this much of the system resources.'"

It may be the new Microsoft business model, low cost software, high cost hardware -- just like inkjet printers (low cost printers, high cost ink)

If Microsoft gets there hands into trusted computer hardware platforms, and ram, they can lock you into platforms that only Microsoft gets money from. And doesn't Microsoft make money from ram now?

Of course the early builds are debugged enabled and fat, but I have no doubt that by the time it is released, it will be much bigger. Microsoft programmers are lazy, why write efficient code when you can just add more hardware? And don't forget that no one will ever need more than 640k.