Hacker News Reader

"Because they can" is often the most fitting answer. Even a tiny feature is worthy to start a totally new project with a fancy name.

View on HN

To be precise, I meant "why not use ..." comparison. I don't mind why the project was started. Whatever the reason, well done for getting it to this stage! But the other side - why should we be interested - is interesting :-)

One reason could be that it might be easier for node.js devs to read and understand its source code. I don't use the software nor have read its source code, though.

Sometimes I think that there are not enough of real problems to solve in the js world.

Too many people pumped into a tight space of the frontend development are creating in there another copy of the whole infrastructure while limited by the tools that weren't designed for that.

Node was designed to build networking applications just like this.

No, node was the realization that JS’s concurrency model could be applied to applications like this.

No? You're not even disagreeing with the parent.

I am, but it is subtle.

Reply on news.ycombinator.com