11–20 of 69 posts
Does anyone know if / when WordPress may start using a modern PHP framework (eg zf2 / symfony2)?
There is a more technical list, including the details on the improvements for developers here: http://codex.wordpress.org/Version_3.5 The biggest thing I wish WordPress would add is a better built in system for real templates, using a something along the lines of Twig ( http://twig.sensiolabs.org/ ). That mixed PHP code and HTML in your standard WordPress template disgusts me every time I see it. I know there are som…
Pity it's so widely used, and there's little competition...
There is a more technical list, including the details on the improvements for developers here: http://codex.wordpress.org/Version_3.5 The biggest thing I wish WordPress would add is a better built in system for real templates, using a something along the lines of Twig ( http://twig.sensiolabs.org/ ). That mixed PHP code and HTML in your standard WordPress template disgusts me every time I see it. I know there are som…
The syntax is very Django/Jinja alike. They took good inspiration.
Meanwhile, why the Wordpress team didn't switch to a template engine and orm after all those years is a true mystery to me.
This would allow future WordPress developers to namespace their code, and out allow simple closures withint your code.
As of PHP 5.5, there is no support for a straight mySQL connection. There is no real downside in WordPress adopting the PDO standard.
There is a more technical list, including the details on the improvements for developers here: http://codex.wordpress.org/Version_3.5 The biggest thing I wish WordPress would add is a better built in system for real templates, using a something along the lines of Twig ( http://twig.sensiolabs.org/ ). That mixed PHP code and HTML in your standard WordPress template disgusts me every time I see it. I know there are som…
Yup, WordPress follows all bad practices of a typical PHP project: mixed PHP and HTML all over the place, lots of global functions instead of classes and direct calls to the MySQL functions instead of PDO so you can't use another database like Postgres. Pity it's so widely used, and there's little competition...
http://trends.builtwith.com/cms provides some good trends of the big players, but I wouldn't put too much stock in it.
That said, as a developer who has fallen into the WordPress business out of necessity, there are a lot of great products out there that are built much better than WordPress and I wish one of them were the dominant player. Still, WP manages to get the job done most of the time.
Earlier quoted context omitted.
weird how I feel in reverse. pseudo languages in templates and restrictive new template syatems annoy me in reverse. I prefer general languages for templating.
The very restrictive nature of a template pseudo language is one of its beneficial attributes. If, for example, you use PHP to create your templates then the very power and flexibility of PHP allows you to make a "quick fix" for a model issue in the template, or a function call from the template, and next thing you know your template is no longer just a view, but instead a messy hodgepodge of code along the lines of…
In contrary, I am in the pursuit for the one universal language to be used everyhere replacing, javascript, html, css, templating language, ruby/python/php, sql..
There is a more technical list, including the details on the improvements for developers here: http://codex.wordpress.org/Version_3.5 The biggest thing I wish WordPress would add is a better built in system for real templates, using a something along the lines of Twig ( http://twig.sensiolabs.org/ ). That mixed PHP code and HTML in your standard WordPress template disgusts me every time I see it. I know there are som…
Yup, WordPress follows all bad practices of a typical PHP project: mixed PHP and HTML all over the place, lots of global functions instead of classes and direct calls to the MySQL functions instead of PDO so you can't use another database like Postgres. Pity it's so widely used, and there's little competition...
There's still plenty of warts, of course, but that seems true of just about every widely used piece of software -- bad decisions early on in development become very hard to walk back later when any of millions of sites/themes/plugins/etc. could turn out to be depending on that bad decision being there...
There is a more technical list, including the details on the improvements for developers here: http://codex.wordpress.org/Version_3.5 The biggest thing I wish WordPress would add is a better built in system for real templates, using a something along the lines of Twig ( http://twig.sensiolabs.org/ ). That mixed PHP code and HTML in your standard WordPress template disgusts me every time I see it. I know there are som…
>> Twig ( http://twig.sensiolabs.org/ ). The syntax is very Django/Jinja alike. They took good inspiration. Meanwhile, why the Wordpress team didn't switch to a template engine and orm after all those years is a true mystery to me.
Does anyone know if / when WordPress may start using a modern PHP framework (eg zf2 / symfony2)?
So yeah, there is some precedent at popular CMSs using a modern framework on server, client, or both. We'll see when and if WordPress follows the example...
Does anyone know if / when WordPress may start using a modern PHP framework (eg zf2 / symfony2)?
Wordpress is its own PHP framework; in fact, PHP itself is a framework, provides everything frameworks do from database querying to templating.