4 ms·
Isn't this the same site from three years ago? Back then, it "aimed to take on Erlang". https://news.ycombinator.com/item?id=2809827 https://news.ycombinator.c
by supporting 12y ago
Isn't this the same site from three years ago? Back then, it "aimed to take on Erlang".
https://news.ycombinator.com/item?id=2809827 https://news.ycombinator.com/item?id=2809827
... and tried to fork Node's EventEmitter into "EventEmitter2":
http://blog.nodejitsu.com/distribute-nodejs-apps-with-hookio/ http://blog.nodejitsu.com/distribute-nodejs-apps-with-hookio...
This time it's "HTTP Microservices", eh? Maybe next time it'll be even more incredibly powerful and surprisingly simple.
- _Marak_ 12y agoThat's an entirely different project from Nodejitsu. I don't know if it's still active. The hook.io domain actually expired and went to public auction recently and I was able to purchase it.
- supporting 12y agoUm... If it was an "entirely different" project from Nodejitsu, then why was it your project four years ago: https://news.ycombinator.com/item?id=1666304 https://news.ycombinator.com/item?id=1666304
- larsmak 12y agoGive him a break, this is how projects - and especially personal projects - develop. You find a cool idea you want to explore on, the end product might be something totally different then what you started with.
- masukomi 12y agoYes, but you don't typically replace the same domain with two totally different services. You create 2 new domains. I would never pay someone for a service when they've repeatedly shown that they're willing to throw out the system people have started depending on and replace it with something radically different. Not only can I not trust the stuff to stay around, I can't trust the developer to have enough of an attention span to care about the old stuff enough to even just leave it alone to keep working in maintenance mode.