48
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Nov 2023
48 points (100.0% liked)
Asklemmy
43893 readers
738 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Some of the devs around Linus are getting warmed up to the idea of a microkernel. Statistics have shown better boot times and better overall performance. As they put it "guess Tannenbaum was right all along" ๐.
Anyway, it should just be a matter of time now. Linus doesn't like the microkernel idea because it risks stability for the sake of modularity. You maintain the entire code base with a monolithic kernel (drivers, FS, everything), while with a microkernel, you just maintain the kernel, everything else is modular, maintained by someone else, thus, things can go bump in the night. The former is better for stability.
Don't break userspace.
Yep, his main motto ๐.
Those are not really the same thing. You can still run something as a microkernel and maintain it as code bases completely under your control and developed in lockstep or even in one giant repository if you really want to.
Microservices and microkernels are not really that similar. The great advantage of a microkernel is not so much the separation of concerns but the fact that less code needs to run unsandboxed in kernel space where every bug can potentially corrupt other parts of the kernel or lead to security holes.