News for hackers. Stuff that matters.
Re:Kill your index.php by krapp on Tuesday January 28, 2014 @09:47PM (#7141509)
Don't you need an index, or something approximating an index? Having an index lets you redirect requests which aren't to public resources (images, js, css) through that single point and by extension the url router. That's what it's for.

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.

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.
Re:Kill your index.php by krapp on Tuesday January 28, 2014 @10:58PM (#7141766)
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.
Re:Kill your index.php by teraflop on Tuesday January 28, 2014 @09:49PM (#7141520)
The article isn't saying you shouldn't have an index.php, it's saying that it shouldn't be part of the framework.
Re:Kill your index.php by krapp on Tuesday January 28, 2014 @10:02PM (#7141560)
Alright, I clearly didn't read the article well enough.