4 ms·
Always. Frameworks are just tools. Typically, when building large JavaScript applications I prefer to avoid the unnecessary dependency nonsense. I understand
by austincheney 9y ago
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.
- nenadg 9y agoCan you explain 'unnecessary dependency nonsense'?
- austincheney 9y agoIf 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.
- nenadg 9y agoHow do you measure 'health' of your application, if you write from the scratch with community removed?
- austincheney 9y agoLots of validation tests. Prove your application does everything it says it does with as many known variants as possible.