Does it matter that "Linux is bloated"?
Summary: Yesterday at LinuxCon, Linus Torvalds founder of the Linux kernel, made a few comments about Linux usually reserved for Windows: "Linux is bloated!"
Yesterday at LinuxCon, Linus Torvalds founder of the Linux kernel, made a few comments about Linux usually reserved for Windows:
"Linux is bloated!"
It gets worse ...
"We are definitely not the streamlined, hyper-efficient kernel I envisioned when I started writing Linux."
And ...
"The kernel is huge and bloated, and our icache footprint is scary. I mean, there is no question about that. And whenever we add a new feature, it only gets worse."
OK, harsh words, but does it matter? Well, from the point of view of the user I don't think it makes any real difference. In fact, the bloated nature of the kernel might actually help Linux compatibility. Given the wide variety of platforms that Linux can run on, it's hardly surprising that the kernel isn't "streamlined" or "hyper-efficient".
According to Torvalds, the it's not causing much problems with regards to stability:
"I think we've been pretty stable. We are finding the bugs as fast as we're adding them, even though we're adding more code."
From a developer perspective a messy kernel will make things more difficult to update the kernel. But then again, in a situation where a project is constantly on the grow, adding new features is sexier and take priority over tidying up existing code. In fact, getting developers to go back to basics can be an uphill struggle.
But it is interesting to see how open source is vulnerable to the same problems associated with bloat in the same way that commercial projects are. What I think is interesting is how as Linux has become bloated, both Microsoft and Apple have been working hard at optimizing code and tidying up their code.
Bottom line though, unless code bloat is at the point where end users are affected by it, then it's not really a big deal. Bloat from the perspective on the user, and bloat from a developer's point of view are two very different things.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
well compare to what
lack finesse
compare to win 2k
compare to win xp
compare to vista /win 7 will all there crapware
compare to Mac and its hardware lock in
Its easy to state Linux is bloated but on
what ....
the vision the Linus add back then ....
Linux is bloated maybe in the end it change
what performance , usability , bloated what
.....
Maybe I am misunderstanding you
I think he's arguing that it isn't bloated
Bloated Linux
compared to an OS sitting on a devastating exploit for 8 years
Compared to
The exploit that nobody has exploited since 2.4 because, well, it took those blind-eyed researchers to find and and back track it to 2.4 while nobody was actually, well, exploiting it?
That exploit that nobody has been doing anything about except for patching it as soon as it was discovered? The exploit that is fixed if people bother to update?
Do try to keep up, please.
BTW...
It affects local privilege escalation.
Physical access has, and always will be, the mother of all security risks.
That goes for all operating systems.
Well, duh. That's what you get with a monolithic kernel
now it's come back to bite him in the butt.
Excuse Me ?
On the other hand, as I learned in MY CS courses back in th 70's, that the best OS is one designed specifically for that piece of hardware, SO my kernel's tend to be a MONO kernel custome configured for what I am running it on.
While try, there ARE probably WAY more modules / drivers /low level routines than what is really needed and it all adds bloat, but makes the kernel pretty much run on anything.
It has to be for performance reasons
If microkernels were easy...
Scaling up a microkernel to be as functional as Linux or Windows or OS-X grows exponentially. Here is from a person who is very PRO microkernel.
http://www.osnews.com/story/14353
[B]And here we encounter the double-edged sword that is a microkernel; the easier a muK is to maintain on a local level, the harder it is to maintain on a global level. [/B]
That's why microkernels live in embedded and simple, ultra fast ultra reliable niches.
All the code is available for the entire kernel in Linux, you literally have every piece of code for every function available, so if it could be converted to microkernel architecture, it would have been already. I would suggest that duplicating the current 6M lines of kernel code into true microkernel architecture (keep in mind, "all" you have to do is subdivide it) would take a thousand coders 2 years, and be truly, globally, unmaintainable.
TripleII
Stil there should be an alternative.
Take a look at Haiku
http://www.haiku-os.org
Fast, loads quickly, micro-kernel designed for responsiveness, multi-threaded, great performance.
After many years of hard work it's now an alpha release, they need developers to jump in and help.
BeOS
Haiku
ummm
I will admit that I have had an eye on Haiku for a while. I am rather interested in what ideas are forthcoming for R2, given how they have been working for years on R1 it would be nice to see if there are any ideas going forward.
Haiku is better then what some think...
Lastly "given how they have been working for years on R1" My friend it's new.. really all new.. It's not BeOS with some code slaped on it. Building an OS does take years. The developers have worked hard without getting payed to bring Haiku where it's at. Give it 2 years and see where they will have it.
RE: Does it matter that
Or embedded.
That might not impact the developer experience but on cheap hardware it would improve the user experience.
:)
Bloat means "full of useless stuff" such as gas!
I wish it was easy (and automatic) for the "non-programmer" to compile a lean fast kernal on the fly for the hardware installation at hand.
Agreed- that would be pretty cool