5 ms·
So? I don't think TJ wrote his post just for the sake of complaining or comparing Node with Go. He had a decision, and had to tell the community he was leaving
by eknkc 12y ago
So?
I don't think TJ wrote his post just for the sake of complaining or comparing Node with Go. He had a decision, and had to tell the community he was leaving because, you know, a lot of people uses his modules. I rely on a couple of his modules and I liked that he took some time to explain why he'll not be working on them anymore.
This post is no more interesting than blogging "I'll keep drinking my morning coffee.. Just as always."
- chdir 12y agoAgreed, on the other hand it is OK to disagree with the shortcoming in node (from previous post) & point them out. It's important for the community to not lose faith because one star dropped out.
- currysausage 12y agoYeah, but it's hosted on Medium, so it looks beautiful and weighty. (scnr)
- ericclemmons 12y agoPosts like this are warranted because some took TJ's move to Go as "jumping ship" on Node, especially when he expressed concern over Node's future. The author correctly frames it as a personal decision in which tool to use for which job.