DEV Community

Discussion on: Why You Shouldn't Use A Web Framework

Collapse
 
victorsaly profile image
Victor Saly

Disagreed, we need frameworks to evolve and make better bikes. And yes some frameworks only exists because the current language in the marker can't cope with the requirements of today business.

But, yes, I can agree that frameworks bring an extra layer of unnecessary functionality, but if you really understand what you are doing, you can use a framework and native code to get the most of it.

If I have the budget of GitHub, I'll probably go native, but in the real world we need some layer of compromise and allow frameworks to help us build solutions; good solutions.

I do use different frameworks at the enterprise level, and they do bring stability, philosophy, methodology and level of continuity in the code base.

I'm a big fan of few frameworks, and I'll rely on them until they prove to be obsolete rather than expending my coding career trying to build a bike from scratch when I can bring a proving bike model into a new level of form...