Ah, the fresh green pastures of a new project. A simple File -> New is all that stands between you and a whole new world of possibilities. It’s a glorious world. A world where only the latest libraries and dependencies will be a allowed. A world unhindered by technical debt or legacy code. A world where 100% test coverage this time definitely will be implemented. Behold, my comrades, a developers utopia.
But you shall soon (again) realise that like all utopia’s, this one can also only be build and sustained by the hand of tyranny. Your own tyranny. And like all tyrants, you too shall be the cause of your own undoing, unable to control the intricate machinery that is your application’s growth. Your application will slowly begin to foster undercurrents of resistance against you and rebelliously dethrone you as it’s self-proclaimed leader. Your code is now in charge and commands you to do it’s bidding instead of the other way around.
1. Why do you want to use a front-end framework? What value does is add to your project?
2. Can my team support it?
Does your project need a front-end framework? The answer will be no 90% of the time. This is not to say that front-end frameworks are not any good. They are good when used in the right way and for the right reasons. Be mindful of having too much of a good thing though. Keep it simple, as always.