Slashdot Mirror


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.'"

10 of 758 comments (clear)

  1. Who cares about RAM usage by PhrostyMcByte · · Score: 1, Troll

    Most systems now have 512MB, in two years they will probably have 1GiB or more. I've got 1GiB in mine right now.

  2. System resource usage by Eric+Smith · · Score: 0, Troll
    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.
    How is it obvious that the resource utilization will go down? When they add more bloat, the commit charge gets bigger. No surprise there.
  3. Report from the inside. by Lord+Graga · · Score: 0, Troll

    Okay, I know a dude who recently got Longhorn installed on his machine, because he's inside the M$ business.

    He reports:
    - It's totally unstable. - It is unuseable on his 2.6 Ghz machine with 1gig of ram (as far as I remember)

    I do not know which build, but it's probably still hella unstable, and seriously what can we use their RAM muncher numbers for when the system is unstable, filled with debug, and probably won't look much like it when it's done?
    Still it's nice to hear a "status report", I love those little gems ;)

  4. Re:OS "improvements" by ultrabot · · Score: 0, Troll

    Does anyone else see the irony in this person using the term lean in relation to the Linux kernal?

    Probably some w2k-running BSD fanboy would. Why do all the Microsoft apologists run BSD instead of Linux? Overcompensating because of their penis-envy, perhaps?

    Pretty much any Unix kernel is pretty lean. POSIX is lean, and simple. The OS might resort to some complexity to get performance, but the bloat should stay within tolerable limits if POSIX is all you want to support (instead of all kinds backwards compatibility hacks and DOS 2.11 compatibility).

    --
    Save your wrists today - switch to Dvorak
  5. Slashdotted, so I'll have to speculate by Snork+Asaurus · · Score: 1, Troll
    At idle, with no applications running, the commit charge is at a whopping 483 MB

    Of which 256 MB is related to DRM?

    --
    Sigs are bad for your health.
  6. Re:Apple by Gannoc · · Score: 0, Troll

    Believe it or not, I think Windows 2000 / Windows XP is as stable as linux / Freebsd. I didn't say better, I didn't say more secure... but I think the stablish issue is mute.

    1) Thats "moot" not "mute"

    2) You're incorrect.

  7. How about the site? by r.jimenezz · · Score: 0, Troll

    Does anyone know if it's a debug build as well? Its commit charge seems to tend to infinity at this time :P

    --
    The revolution will not be televised.
  8. Obviously? by frovingslosh · · Score: 1, Troll
    Obviously, the final release or even the beta releases will not consume this much of the system resources.

    Bullshit.

    --
    I'm an American. I love this country and the freedoms that we used to have.
  9. Re:Nearly 500 meg? by imsabbel · · Score: 0, Troll

    Well, my raid array is 3.5 MILLION times as large as the floppy of my first computer (cpc6128).
    RIDICULOUS!!!!!!1111

    And YOUR OS is FOUR HUNDERED TIMES BIGGER then cpm 2.1

    --
    HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
  10. New Internet Explorer features by srcosmo · · Score: 0, Troll
    Ah, it has a popup blocker, and a download manager!!

    Where would we be without MS innovations?

    --
    free speach
    Did you mean: free speech