Closed SpindleMonkey closed 7 years ago
In my opinion, often too much emphasis is placed on finding the best framework to solve a specific problem. This is probably the most important part of choosing a framework, but an often-ignored close second is "what are you familiar with, and how similar is that to this new framework you're going to learn?"
If I were deciding between React and Angular, for instance, I'd need to know how familiar my team and I are with JSX (React), Typescript (Angular), State Management (React), Observables (Angular), ....
Next, I'd think about that important part of "what am I building?" I usually google for good tutorials solving close to my problem like "Angular Email Forwarding App". I measure quantity (10 google results from distinct sources is better than 2) and quality (try one of each of the tutorials...often these tutorials have out-of-date or unclear directions, follow your gut on which one is more comfortable).
Everyone is biased when it comes to frameworks, which can be frustrating, but once you find something you're comfortable with, stick with it for a while, rather than jumping between frameworks and their feature releases.
Something that's well worth looking at is TodoMVC, which has an identical Todo app, built in all the most popular frameworks.
Did that answer your question?
It does--that link is great & I've bookmarked it for the future when I'm asking this question again ;)
I've found the following:
So these articles cover several frameworks, but how do you know if you're looked at the best frameworks for your application? Maybe what I really need to know is who should I trust for framework info?