Sure, that's why I said that in asm you usually design it differently from another perspective -- that's where some major optimizations get place (sometimes we can't figure them, but they are there, waiting just to be discovered )

Just becasue we have really fast computers and really big harddrives nowdays doesn't mean that a small hello world program that takes ~10-20kb isn't bloat. becasue it is.
without this kind of bloat we wouldn't need any dual core 3ghz computers with 2gb of DDR2 ram, or even a 350mhz with 128mb ram.

Wrong. It's true you wouldn't need that much for a lot of standard "office style" applications, but there's plenty of situations where you *NEED* all the computing power and memory you can get. For the home sector, though, games are the driving force... and while they might not be extremely efficiently coded, games of today use some pretty sophisticated code (AI, Physics) that *does* need a lot of computing power.

Not to mention the size of the datasets necessary - huge textures, bumpmaps, lightmaps, detail textures, mipmaps, very complex level and model geometry, et cetera. You could reduce a lot of that on-disk (if you can accept slower loading times), but all this data *does* require quite an amount of memory.

It's not the "10-20kb hello world" that is bloat. It's rendundancy (like Delphi, BCB, MFC programmers linking statically to their libraries instead of dynamically), it's inexperienced programmers using bad algorithms, and it's the time-to-market pressure by your boss.

MenuetOS is actually pretty kewl, Even though I am new to assembly, I admit the sound blaster code left a lot to be desired, but all in all its awesome to see what can be done, and what the potential is. If anything it provides others with a starting point to improve on. However in the meantime if anyone knows of a perfectly optimized os with no bugs let me know, until then I have no complaints about MenuetOS and what it may currently lack.