Linked by Thom Holwerda on Mon 14th Sep 2009 06:04 UTC
Thread beginning with comment 384069
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Ah, OK. Is that also the reason why Haiku (compared to BeOS 5, not by today's standards) is so huge? By default, 1GB HDD used and 128 MB RAM minimum. R5's requirements were a quarter of that.
Disk-wise, yes... there are two complete gcc toolchains, and two sets of OS C++ libs...
There's also a *lot* of pre-packaged stuff that BeOS didn't have, such as Firefox (a pig), lots of GNU stuff (autotools and friends, etc.) Python (huge), and a multitude of other things thrown in.
As for memory, Haiku can boot with like 32-40mb, as long as swapfile is enabled. A lot more memory has been devoted to disk caching, extra resources available for the kernel, etc. Haiku doesn't use quite as many dirty-tricks to keep things tight, as most of today's computers are powerful enough to prevent that... of course if things must be optimized further, they probably can be
In other words, take it all with a grain of salt - expectations of an OS today are higher than they were in the BeOS days, so Haiku has to live up to those expectations somewhat, and using more ram/disk space seems to be a reasonable compromise still...




Member since:
2005-07-06
Ah, OK. Is that also the reason why Haiku (compared to BeOS 5, not by today's standards) is so huge? By default, 1GB HDD used and 128 MB RAM minimum. R5's requirements were a quarter of that.