He isn't trying to rethink the desktop/workstation OS. If he's found a way of improving upon existing desktop environments, it should be clear what improvements he's made and how he has made them.
It seems it's written in Node Webkit (NW.js), which - if I understand correctly - allows you to build desktop applications in the same way node.js allows you to build applications which run in the browser. He appears to have used this to prototype a desktop environment. Rewriting a desktop environment, for efficiency, in C and using Xlib would itself be a major undertaking.
It's a statically typed subset of JS that uses typed arrays for machine-typed memory and JS's bitwise operators for int32 and uint32 casts, and + for to-IEEE754-double, etc.
It is as fast as memory-safe C-like variants already, see
https://arewefastyet.com/#machine=29&view=breakdown&suite=as...
https://arewefastyet.com/#machine=29&view=breakdown&suite=as...
I'm not sure why the native C++ (clang) gray line stops over a year ago. Perhaps @azakai can say.
/s
Very, very far from C in memory, for all things.
He's very creative. Both his video[0] and website are very artistic. I originally went through the initial reddit links[1] to try and figure out what he was trying to do here.
He just needs to provide more substance. Lots of flash but little info. I say this as constructive criticism. It shouldn't have taken me as long as it did to figure out what this was.
On a positive note: I did spend extra time trying to figure it out because it looks so great and I really liked that he went JS-stack with this - it's very impressive. Impressive enough that it's on my todo list (very few things get on it because I've gotten very lazy!:)
It's not criticism, an actual full operating system written in NW.js would just be very special in its own way.
NW.js requires an underlying operating system to function, so if it really could be called an "NW.js-based operating system", there would have to be interesting things like bootstrapping WebKit as early as possible and then doing everything else in there.
And that would also have stark performance implications. If core-libraries were written in NW.js, getting something as fluid as in the videos, would be absolutely incredible.
> if this gains traction it would likely be rewritten and optimized for better efficiency
Uttered by any JS "mvp" apologist ever; number of times fulfilled in JS projects: 0.2 times. (The .2 goes for Atom and its C++ rewrites).
Also bear in mind this is a single university students design project, he's not trying to be Linus or stallman just yet - Id love to see more people trying to rethink the desktop/workstation OS.
To the author - well done, this is far more than I would have been able to do in uni!