Re:Kill your index.php
by erichurkman on Tuesday January 28, 2014 @10:44PM
(#7141718)
Access to static, public resources (images, js, css) should not be run through any dynamic language. Let the web server do what they do well: serve files. Or better yet, push that junk to a CDN.
Yeah, I wasn't clear, sorry, lack of sleep. It's usually .htaccess that either serves the static file or routes requests which don't hit a resource into index.php... but to me, that process, including .htaccess and an index file, would have to be an integral part of the framework.
The article isn't saying you shouldn't have an index.php, it's saying that it shouldn't be part of the framework.
I actually don't mind an index.php with some gnarly procedural code. Sometimes code has to do what it has to do, and it doesn't always have to be pretty.