2 ms·
From that perspective, I see your point. I think Angular had an optimal sweet spot for the scope of applications it was good at building. Once you went past tha
by chrisco255 9y ago
From that perspective, I see your point. I think Angular had an optimal sweet spot for the scope of applications it was good at building. Once you went past that point, it became unwieldy. I don't think you should chase something that's merely 12-24 months old if you're working on production code for a big product. But to some folks, using Golang or Node.js is considered "hipster" even though those technologies have been out now for many years and have proven themselves at scale at large companies. I wouldn't have suggested using Node in 2010, but in 2017, it's a mature choice. And letting your team use something like Go or Node over Java isn't going to kill you and you may very well see productivity gains and recruiting gains.