@mcc
i think react's main problem is that the kernel is pretty primitive compared to linux
support for smp isn't something you should try and add after decades of work
@hikari

@7331 @mcc oof i didn't know they hadn't got that far, but this isn't so surprising really. it's a hobby project for windows kernel enthusiasts with no prospects of enterprise support (they pay for windows), and kernel enthusiasts are a tiny group that probably mostly work for microsoft, work for driver vendors, have been contaminated by research access to microsoft code, or… work on malware

@hikari
as a kernel enthusiast (TM) i can tell you that yea, there's not too many people who like to work on that sort of stuff (and most - like me - just roll their own because it's way more fun and even more abandon their projects early on because it's a lot of work) and i can't imagine it was a lot easier in '96 xD

so i guess i can see why features that did have an immediate impact on usability (e.g. writing a usb stack) were prioritized over getting the architecture right but the problem there is that it's extremely hard to go and change this sort of stuff later on (a lot harder than changing the architecture of normal software imo) and even harder if you want your implementation to be performant and sane
@mcc

@7331 @mcc yeah. i also think people don't appreciate enough that big architectural changes are fucking hard work and the most reliable way to get them to happen is to pay a team of people to work full-time on it. it's very difficult for actual hobbyists to get that stuff done