News for hackers. Stuff that matters.
Re:NO-Framework approach to PHP by krapp on Saturday October 22, 2016 @04:38PM (#12770459)
..and when you try to extend this to something reasonably complex, including third party libraries and a database, you'll realize why people stopped writing PHP like this years ago.
Re:NO-Framework approach to PHP by rubyfan on Saturday October 22, 2016 @06:43PM (#12770907)
The actually looks like a simple single controller action using a view model. Nothing really stops you from implementing other abstractions like ORMs, state machine, authentication, web service calls, etc.

I actually think you could build a relatively well organized large project with not much more than this really needed.

Re:NO-Framework approach to PHP by krapp on Saturday October 22, 2016 @07:17PM (#12771029)
You could, but I suspect that inevitably you would wind up having written a framework to organize and manage that complexity, just an ad-hoc and poorly designed one.
Re:NO-Framework approach to PHP by rubyfan on Saturday October 22, 2016 @08:12PM (#12771212)
True enough, building crappy over engineered frameworks in big projects is inevitable ;-)
Re:NO-Framework approach to PHP by slim on Saturday October 22, 2016 @05:33PM (#12770672)
If this is not a joke, op is really a victim of framework formatting of his brain. That render() function rendering <?=> tags is just.. I don't know.
Re:NO-Framework approach to PHP by rubyfan on Saturday October 22, 2016 @06:20PM (#12770827)
It's been a while but isn't <? and <?= standard PHP?
Re:NO-Framework approach to PHP by slim on Saturday October 22, 2016 @08:41PM (#12771291)
Actually it's <?php but it's the same
Re:NO-Framework approach to PHP by rubyfan on Sunday October 23, 2016 @06:50PM (#12775815)
<? and <?= and "short open tags" supported optionally on older version but I think enabled by default these days.
Re:NO-Framework approach to PHP by slim on Saturday October 22, 2016 @08:40PM (#12771284)
Indeed