> Because reworking userland is still easier than getting meaningful hardware support in a new kernel. Our kernel has "pretty good" hardware support already.

> Because reworking userland is still easier than getting meaningful hardware support in a new kernel. Our kernel has "pretty good" hardware support already. > Unless you own nothing but old Thinkpads, hardware support is usually questionable at best on operating systems more "alternative" than FreeBSD. Haiku boots and runs pretty well on Ryzen 7 boxes and Hades Canyon NUCs from last year (with working USB, network, WiFi, etc.) And we also support old ThinkPads, too :) > I guarantee that there is not a single computer in my house where all hardware supports all primary functionality under Haiku, where they all "just work" on Linux. Unless you only own machines stuffed with Broadcom and NVIDIA hardware, this is almost certainly false. There are a few quirks to be aware of, but Haiku largely boots and can at the very least connect to the internet on just about anything made in the past decade and a half. (We reuse FreeBSD's ethernet and WiFi drivers, so any network device that works under FreeBSD should work under Haiku.) > And then of course you still have to deal with all the pain of rebuilding your applications for the new OS Haiku is POSIX-compliant and has a lot of Linux toolkits and libraries ported (Qt, wx, OpenSSL, libuv, SSH, WebKit, ...) So a recompile may be all that is needed. > so you've saved absolutely nothing while adding a lot more effort to achieve parity. But you have gained a fully integrated desktop environment instead of a system of disparate projects tied together with duck tape and superglue.