Live data from Hacker News

The Jury Is In: Monolithic OS Design Is Flawed [pdf]

ts.data61.csiro.au

61–70 of 199 posts

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#61
post #45

Earlier quoted context omitted.

The dirty secret is that we take a microkernel, rename the syscalls as "upcalls", throw in some hardware emulation code as a less efficient and uglier API for software that can't be bothered to be ported, and call it a hypervisor. Also, your phone's baseband processor almost certainly runs a microkernel, and likely so does your car.

and according to someone, your Nintendo console too It's quite crazy to count all the layers cpu microcode cpu isa hypervisor os kernel userspace api browser runtime js vm application your mouse I want my 386 back

If you mean the Switch, yes it is a microkernel, so fast enough to play all those flashy Vulkan/NVN games.

https://media.ccc.de/v/34c3-8941-console_security_-_switch

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#62
post #27

Earlier quoted context omitted.

It's better to have buggy, incomplete drivers than no drivers at all.

This is your opinion. I prefer using hardware with stable drivers, working reliably.

That's why I use a Mac. Seems like a good solution is to have the OS and HW manufacturer to be one and the same.

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#63
post #53

I'd hazard to say that every design is "flawed" in some regards: there's no way to achieve all desirable qualities and none of undesirable qualities. For one, some desirable qualities contradict each other. So "${thing} is flawed" is not precise enough; an interesting statement would be "${thing} is not the best choice for ${conditions}". A monolithic OS is not the best choice for a high-reliability system on unrelia…

> In other words, the ancient concept of "right tool for the job" still applies.

Or use a multi-tool ;)

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#65
post #19

Earlier quoted context omitted.

the Hurd-verse lives! Richard Stallman is a clean-shaven, foulmouthed autocrat, and Linus is composing folk songs about joining hands with Intel and Nvidia!

Who is dressing up as a monk?

Corey Doctorow. And Eric Raymond wears horn-rimmed glasses.

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#66
post #53

I'd hazard to say that every design is "flawed" in some regards: there's no way to achieve all desirable qualities and none of undesirable qualities. For one, some desirable qualities contradict each other. So "${thing} is flawed" is not precise enough; an interesting statement would be "${thing} is not the best choice for ${conditions}". A monolithic OS is not the best choice for a high-reliability system on unrelia…

man, a lot of words to say nothing...

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#67
post #63
post #53

I'd hazard to say that every design is "flawed" in some regards: there's no way to achieve all desirable qualities and none of undesirable qualities. For one, some desirable qualities contradict each other. So "${thing} is flawed" is not precise enough; an interesting statement would be "${thing} is not the best choice for ${conditions}". A monolithic OS is not the best choice for a high-reliability system on unrelia…

> In other words, the ancient concept of "right tool for the job" still applies. Or use a multi-tool ;)

Multi-tools - for when you need to do a mediocre-to-bad job with lots of different things!

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#68
post #63
post #53

I'd hazard to say that every design is "flawed" in some regards: there's no way to achieve all desirable qualities and none of undesirable qualities. For one, some desirable qualities contradict each other. So "${thing} is flawed" is not precise enough; an interesting statement would be "${thing} is not the best choice for ${conditions}". A monolithic OS is not the best choice for a high-reliability system on unrelia…

> In other words, the ancient concept of "right tool for the job" still applies. Or use a multi-tool ;)

The trade-off with a multi-tool is additional complexity, more difficult maintenance, it's heavier, takes up more space, etc.

Re: The Jury Is In: Monolithic OS Design Is Flawed [pdf]

#70
There is a reason why kernel code run in privileged mode, speed! If you run more kernel code in privileged mode then you do not need to copy as much data between the kernel and user space. Vs a micro kernel you will have to copy more data up to user space. Copying data to user space causes context switches and gives less performance.

Larger mono kernels: Speed

Micro kernels have advantages such as: smaller privileged attack surface and thus more secure, more crash proof as you can restart user land processes for example device drivers

https://en.wikipedia.org/wiki/Microkernel

Post reply on HN