NO-Framework approach to PHP
github.com
NO-Framework approach to PHP
1–10 of 10 posts
Re: NO-Framework approach to PHP
#2..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
#3If 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
#4If 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.
It's been a while but isn't <? and <?= standard PHP?
Re: NO-Framework approach to PHP
#5..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.
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
#6..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.
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.
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
#7Earlier quoted context omitted.
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.
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.
True enough, building crappy over engineered frameworks in big projects is inevitable ;-)