Skip to content

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


You know what, frameworks are the reason I say I'm not a front end dev.

I can do nearly anything reasonable, and some less so, in sql alone-just give me enough time ok?

Today we had to duplicate a spreadsheet of aggrated results with um.... Just html and the result set. This set is a table whose entire content is a single result. 216 cells worth.

We generated the entire table in maybe 30 lines of c# and some dog simple css.

Its really rather nice, it's readable, we can maintain further pages this way.

And yet we are novices at html, css, and hardly ever touch javascript.

The work is worth money to someone.

Over complicating the front end is what my perception of frameworks is. If all I've got to do, to be a front end dev, is do a decent job of generating reasonable html and know my css, I can manage that.

code of conduct - report abuse