5 ms·
> a step backwards towards in-page PHP In-page PHP is ugly, but it sure let normal people who had gotten comfortable with serving static HTML make dynamic web
by core-questions 7y ago
> a step backwards towards in-page PHP
In-page PHP is ugly, but it sure let normal people who had gotten comfortable with serving static HTML make dynamic web pages quickly. It's also highly performant.
- aylmao 7y agoLee Bryon had a fantastic talk about this during the last React Conf, check it out [1]. He talks about the cyclic nature of programming paradigms, and how we might actually be "going back to PHP" and that might not necessarily be a bad thing. PHP does after all have a straightforward mental model and expressive syntax, but now we have learned to build better (more secure, more resilient, performant, better architected, etc) web apps. IMO very worth a watch. [1]: https://www.youtube.com/watch?v=vG8WpLr6y_U https://www.youtube.com/watch?v=vG8WpLr6y_U
- bhhaskin 7y agoI would argue that we have never left PHP. WordPress powers 34% of the web. It's fast and flexible, and modern PHP is actually a delight to work in. It's also pretty secure. You have to go out of your way to make it insecure. Which is an issue with any programming language.
- qwerty456127 7y ago> In-page PHP is ugly Why? Although I agree PHP itself is ugly, I always considered this particular part beautiful and alone worth tolerating the rest.
- Aeolun 7y agoI don’t think there’s anything but in-page PHP. Some files are just skipping the HTML altogether.