4 ms·
Regarding one of the last comments, I'd say the two biggest reasons for using Node over Go, at least initially. Prototyping speed, and a stronger connection to
by tracker1 8y ago
Regarding one of the last comments, I'd say the two biggest reasons for using Node over Go, at least initially. Prototyping speed, and a stronger connection to a web front-end. I've really not seen any other language/platform work faster for developing a huge variety of implementation details than JS/Node. IT's a really good balance of performance, flexibility and ease of development.
Is it a Panacea? Of course not. That said, I think that starting more monolithic an breaking pieces off as needed is a strong approach, best started with Node. From there, you want different pipelines/processes/queues/workers in other platforms, great. Write that piece in go+grpc and call it from your api endpoint server.
So many times I see devs want to go the optimal X, without even considering if "optimal" is needed, and if it's prudent to start with.
- tracker1 8y agoAlso, can always front with gopher (written in go) and defer to other systems via reverse proxy.
- fixermark 8y agoAnd the main reason to not use Node: JavaScript.
- deleted 8y ago[deleted]
- anothergoogler 8y agoWhat a lovely fusion of the blub paradox and a middlebrow dismissal.
- tracker1 8y agoKind of, though your tone seems a bit dismissive. In the end, the Node/JS community, mostly because of npm, has a lot to offer and that is the ability to create a working product more quickly than most other options in most conditions.
- anothergoogler 8y agoPardon my snark! In all seriousness, isn't it possible that you're more productive with Node because you're more familiar with it and its ecosystem?
- tracker1 8y agoNot really, I've also been active in C#, at one point more Java, and a few other communities (Ruby on Railes) along the way. I'm not really tied to it so much as choose it. I've never had the vitriol towards JS that other devs have had in the past, I've always recognized DOM issues vs. language issues, and many of the "good parts" long before the book. In the end it comes down to the massive ecosystem. Which has some drawbacks, but in the end allows for unparalleled productivity gains.
- Scarbutt 8y agoRuby/Rails users will say the same.
- jazoom 8y agoSure, if you ignore everything else in tracker1's original comment, which can't be said for Ruby/Rails.