6 ms·
Exactly. For me, the Node.js name is tarnished. The community hit the ground running with io.js and I believe it should have continued down that road. It would
by izolate 11y ago
Exactly. For me, the Node.js name is tarnished. The community hit the ground running with io.js and I believe it should have continued down that road. It would have come to replace Node.js in due time.
- aaron-lebo 11y agoI think you are an outlier, though. When you are talking about mass appeal, a lot more people are aware of thee node name than io. There is no reason to have to rebuild the branding and awareness process.
- rpwverheij 11y agoI agree. As someone who just helped transition the main product of a company from polling towards socket.io + node.js, I can tell you the main name they know, somewhat understand and praise is "nodejs". To them that's the keyword to what made everything so quick and responsive. If I had to tell them at some point that actually nodejs was a bit behind and now we should move to io.js that would have been a bit confusing at least. Now, I can just be happy that "nodejs" will be the "awesome cutting edge tech" for me aswell as for them.
- josteink 11y agoAs anecdotal evidence: Where I work we use Node in our projects and today is the first time I've ever heard about io.js. Make of that what you like.
- izolate 11y agoYou're not curious about your own tech stack?
- josteink 11y agoWhen "everyone" says "Use node" and every problem you need solve is solvable by googling "nodejs $problem" without anyone every anywhere mentioning iojs as a viable option, you can still be curious about your own tech-stach without knowing about the existence of forks. I think you suffer from a too simplistic view of things.