Always. Frameworks are just tools. Typically, when building large JavaScript applications I prefer to avoid the unnecessary dependency nonsense. I understand, though, there are many developer who lack the confidence to make that choice easily.
If I can write it faster myself and end up with lower maintenance overhead compared to the concerned dependency the concerned dependency isn't needed. This is a major concern of framework applications that intertwine with your logic since removing a framework from your application may mean a complete rewrite of your application.
With production software each and every dependency you do not validate with your integration tests is a risk beyond your visibility.
I frequently hear from JavaScript developers the excuse that a popular application is validated by the community. This is a false validation from somebody who has never worked operations. The community is irrelevant. The only thing that matters is the health of your application, which is something you must take ownership of very directly.
IMO, there's room for a paradigm shift. I've been thinking a lot about this recently: even though these new frameworks (Anglar/React/Vue) have made development easier in some ways, they all rely on dubious and complicated methods to achieve relatively simple things. Often, I find myself missing jQuery.
jQuery was cool for DOM manipulation back in the days. Now I can't imagine writing huge JS application using jQuery. What is your opinion about React or Vue in particular?
8 comments
[ 3.4 ms ] story [ 31.7 ms ] threadWith production software each and every dependency you do not validate with your integration tests is a risk beyond your visibility.
I frequently hear from JavaScript developers the excuse that a popular application is validated by the community. This is a false validation from somebody who has never worked operations. The community is irrelevant. The only thing that matters is the health of your application, which is something you must take ownership of very directly.