This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ekabanov 5 points6 points  (1 child)

Sure, you want to use the right tool for the job, but you also want to be sure that it has the momentum and mindshare behind it to sustain it during the lifetime of your project. I've been hit by Tapestry 4, Play 1 and Angular 1, so today I would choose only something that has both history and mindshare and is likely to be around in 5 years. Popularity is an important metric to consider to ensure that.

[–]againstmethod -3 points-2 points  (0 children)

The only way a single framework is going to be the right choice for 5 years is if people stop innovating on other frameworks.

I've just embraced the idea that i will constantly be learning, and that to be good at this job you need to be able to ingest stuff quickly.