loading...

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

TOP OF THREAD FULL DISCUSSION
re: From 30 years of dev experience I couldn't agree more, David. And yes, I have to deliver quality web apps (and underlying APIs) at pace. I baulk ...
 

Sure, if you want performance then it is good to be 'close to the metal'. High performance is a non-functional requirement that not all of us need, and it is better to focus on the domain than reinventing Knockout, Vue, react, angular, or whatever buzzword framework you want.

I find it hard to believe that writing your own frameworks for large Enterprise projects does not lead to slower development times than using a tested off the shelf solution.

What we should be teaching developers is how to understand when to use the tools available to them, not the equivalent of constructing a table saw every time they want build some furniture.

I worked most of my career as a server side guy and this hostility to frameworks is completely alien to me.

code of conduct - report abuse