No doubt JavaScript's past, present, and future is intertwined with the web, but really it's an independent programming language. It's not like there are primitives for divs and tables.
And by an accident of history, it also happens to be the world's most popular programming language and overall a decent scripting language, so I can't see why its web association should make it any less OS-ready than any other language.
Plus, Node's async model lends itself implementing lower-level OS features (not that they are present so far in NodeOS).
We are forced to use poorly-designed legacy languages on the "open" web, but why would you torment yourself with them when you are not limited outside of the "open" web?
And by an accident of history, it also happens to be the world's most popular programming language and overall a decent scripting language, so I can't see why its web association should make it any less OS-ready than any other language.
Plus, Node's async model lends itself implementing lower-level OS features (not that they are present so far in NodeOS).