This sounds like something which, were it done by Microsoft, would be taken as evidence of terminal senility on the part of the technical leads. What is NetBSD's reasoning for doing it?
The difference being that in this case, it's a doohickey in NetBSD that you can turn on if you're feeling bored or deranged. Microsoft would make it the new paradigm for development and then deprecate it four years later when the next new paradigm came out.
Comments
I run FreeBSD on my home server (because of ZFS). But I use NetBSD every now and then.
Things I like about NetBSD:
- It has support for both Dom0 and DomU Xen domains.
- It is very clean and portable code, you can build it on any *nix machine and get install media, just do ./build.sh release; ./build.sh iso-image
- There are fun experiments being done. Like rump kernels and Lua in kernel space
- It's dominated by hobbyists.
I run FreeBSD on my home server (because of ZFS).
How is it better than the alternatives (linux and other bsds)?
> Lua in kernel space
This sounds like something which, were it done by Microsoft, would be taken as evidence of terminal senility on the part of the technical leads. What is NetBSD's reasoning for doing it?
Rapid prototyping of drivers is one reason.
A recent project adds Lua to Linux for dtrace style functionality https://github.com/ktap/ktap
The difference being that in this case, it's a doohickey in NetBSD that you can turn on if you're feeling bored or deranged. Microsoft would make it the new paradigm for development and then deprecate it four years later when the next new paradigm came out.