re: Why You Shouldn't Use A Web Framework VIEW POST


this wheel doesn't come with a whole bunch of crap you'll never use

Have you heard about dead-code elimination? Tree shaking, which does it, is a standard and is enabled by default in major bundlers like webpack. You'll never include code you never use.

Also, I disagree that you can easily get by with just the standards. Unless you include big polyfills, you will have problems with browser support, hence, you betray your users. If you include polyfills, what's the difference between including a polyfill and a framework? Often they are comparable in size and performance impact on your users. For example, what's the difference between including Custom Elements polyfill and React?

Another great benefit of using a framework is that it helps you have a proper architecture, which is a point you completely missed in the article.

code of conduct - report abuse