News for hackers. Stuff that matters.
Re:What is a Web Framework? by twistedpair on Tuesday March 04, 2014 @03:09PM (#7342744)
The purist approach is nice, and we've all been there, but eventually you'll want to pool those db connections for speed, to comprehensively handle security, and to do things Apache does not do with the URL's like dynamically register/unregister paths in URL's that have no concrete corresponding script file.

Of course you can attempt to add those things yourself, but the best code you'll often write is that code you don't write at all because someone already did. Don't reinvent square wheels.

Re:What is a Web Framework? by oneeyedpigeon on Tuesday March 04, 2014 @04:58PM (#7343509)
Or you could keep your markup out of the database and db connections become a non-issue (granted, I'm talking about the 99.9% of websites that are content-centric as opposed to web apps).
Re:What is a Web Framework? by gaius on Wednesday March 05, 2014 @04:46AM (#7346175)
We were doing all of those things in the 1990s.

For many "developers" these days the job consists of trawling the Internet looking for a "framework" that matches their project, then tweaking it.