I'm not saying to use what frameworks win in popularity. The problem is; how are you supposed to know which framework/library tool is going to be the best for your project without actually trying it in said project? I've heard a lot of stories of startups going down a path of using a new library because they initally thought it would be the right tool to fit their needs, but after actually implementing it they find it was the worst decision they ever made. They inevitably end up needing to rewrite everything (eventually) using the more appropriate tool.
Comments
You should not ever, under any circumstances, apply the 'next big thing' to your project if your criteria for success is "other people are using it".
You should evaluate your needs and pick a tool based on those.
There aren't "winners". There are tools. Some of them are more effective at certain things than others.
If you are asking how to evaluate "which framework is going to win", then I'd argue you have no business making these decisions.
I'm not saying to use what frameworks win in popularity. The problem is; how are you supposed to know which framework/library tool is going to be the best for your project without actually trying it in said project? I've heard a lot of stories of startups going down a path of using a new library because they initally thought it would be the right tool to fit their needs, but after actually implementing it they find it was the worst decision they ever made. They inevitably end up needing to rewrite everything (eventually) using the more appropriate tool.
With that said, I'm looking for advice on how to avoid that scenario, but yet stay current with tech.
Prototype!