top | item 3461042

(no title)

oakgrove | 14 years ago

"75%...drivers...filesystems...it does seem to be getting quite bloaty"

Does the code that supports those drivers and filesystems slow the overall system down in any way? If not, how can you call it "bloat"? Bloat in this context generally means additional code that is out of proportion to its functionality while also using a disproportionate amount of memory and diskspace. There is legitimate bloat in the linux kernel but suggesting that that has anything to do with the variety of hardware support is to misunderstand the meaning of the word. Oh yeah, YMMV

discuss

order

Craiggybear|14 years ago

Look ... 95% could be pure Assembler. OK?

No, its largely irrelevant nowadays. But there's a pile of cruft in there that could go ...

I'm not critiquing ANYTHING about the kernel. BUT. There IS a HUGE pile of crap still in there and everyone knows it. Don't nitpick my innocent and uncritical comment and try to turn it into a major critique of the kernel. Its still WAAAAAAYYYYY superior to the shite that still exists in Windows (because it simply MUST).

NO. Of COURSE it doesn't slow down the Linux experience but it might one day become too large to be realistically distributed without a lot of trimming.

I've been a major user, developer and proponent of Linux for decades. I use nothing else in my day to day life. Don't dare to presume to pull me up because I dare to comment on a seriously discussed and current problem with the current kernel. NAMELY: IT'S BECOMING A FAT BITCH AND EVERYONE KNOWS IT.

It's still and always will be my OS of choice. Whether or not I knew how to exclude certain chunks of irrelevance from my build or not.

derleth|14 years ago

bloat: n. Any feature I'm not using at the moment.