Comment Re:Do something about your hoarding problem (Score 3, Insightful) 983
Not all of us have access to the time machine required to know *which* 1TB that is.
Are you willing to share yours?
Not all of us have access to the time machine required to know *which* 1TB that is.
Are you willing to share yours?
Commenting to fix mis-mod - accidentally modded flamebait, but sublime was the first thing that came to my mind as well.
Off-topic - this was actually the one thing I thought the beta made better, the left/right split of positive/negative mods as well as larger hit boxes, I think it will reduce this kind of error in the future (I mean.... #betasux).
The benchmarks on Phoronix did temperature, and commented on (though didn't measure) noise. Was actually a fairly comprehensive, well done benchmark, the only thing missing was frame latency measurements.
Yeah, but it tab completes, so on the other hand it's the only word you have to type and the only spelling you have to get correct.
My biggest gripe with service is that it doesn't support tab-completion.
Just because you can point to one microkernel that doesn't really work, and one monolithic kernel that does, will not invalidate the perfectly valid points made about the benefits of modularization. Yours is just a logical fallacy:
eg. "I'm sure everybody that likes bicycles never drives a car..."
Except it's not valid points made about modularization in this context. It's a blanket statement that modular is better, for which a single counter example is sufficient to disprove. The AC's post didn't mention specific flaws with systemd, instead they asserted generalizations about how modular is better than monolithic. Just because there are potential benefits to a modular system over a monolythic system does not mean a specific modular system is better than a specific monolythic system, leaving the AC's post as little more than FUD.
This is not the point or benefit of the original UNIX and much of the Linux architecture. By doing small tasks well, a reliable toolchain can be built of those small tasks. *OF COURSE* a monolithic megamonster is going to have fewer lines of code than all the different components shoe-horned into it. And of course *it's going to get details wrong* in those individual components, but the monolithic megamonster may rely on those flaws or make debugging of them unreasonably difficult.
I can only assume that all people who support this argument run GNU Hurd, as it's a microkernel, instead of that 16,000,000+ line of code "monolithic megamonster" known as the Linux kernel.
Suggest you just sit there and wait till life gets easier.