[angersock]

Great, more badass rockstar ninja developers using the newly discovered 201x techniques of async coding to disrupt the operating system.

My beef is not that the author is playing around with using an actually pretty awesome dynamic language as an operating environment; it's that the author doesn't explain that what they're doing is actually, you know, an operating system.

How are you booting? How are you writing to the file system--and which? How do you handle multiple users? How do you handle device IO? How about scheduling?

I want so badly to be able to take projects like this seriously, but it can be hard sometimes.

EDIT:

Ah, so, this is just Node sitting on top of Linux ( https://github.com/NodeOS/Docker-NodeOS ). Would've been nice if that was mentioned in the article.

EDIT2:

Hmm...what's the word for it when the OS suspends your program while waiting on IO for it...a sink ro nose? a sink rose? Bah, I can't remember--that's just old boring shit from the dinosaur ages of computing anyways.

[bachback]

It's not a kernel! how hard can that be to understand?

[badman_ting]

I share your cynicism.