Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WordPress 3.5 “Elvin” Released

wordpress.org

Post reply on HN
Print view View original

1–10 of 69 posts

Re: WordPress 3.5 “Elvin” Released

#5

Post by NathanKP »

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 some custom solutions for creating real templates in Twig, but this should be part of the mainstream WordPress branch.

Re: WordPress 3.5 “Elvin” Released

#6

Post by diminish »

NathanKP wrote: post #5

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…

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.

Re: WordPress 3.5 “Elvin” Released

#8

Post by NathanKP »

diminish wrote: post #6
NathanKP wrote: post #5

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…

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 what you often see when you open up the typical WordPress template.

The template pseudo languages enforce a strict separation between model and view, and they typically do so with a much more concise syntax and legible format compared with embedding PHP in HTML, for example.

I used to prefer general languages for templating, but once I learned the pattern of using Twig to the full I found that I could create templates much faster than before, and I could also go back to a template after a couple months of not looking at it and quickly understand what I was looking at.

Re: WordPress 3.5 “Elvin” Released

#10

Post by JeremyMorgan »

NathanKP wrote: post #8
diminish wrote: post #6

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…

This is a very good point. Sometimes those "quick fixes" really aren't the best idea, I myself used to "hack" so much stuff in Wordpress when I was using it, and yes I solved whatever problem I was having at the time, but a few updates later it would come bite me in the you know what.

So much of programming is protecting the programmer from him or herself. By enforcing rules you protect yourself from bad habits. I think a separate template system and keeping the view separate would help keep everyone honest.

Eventually I started to do my modifications as plugins, which is one area where Wordpress really shines. Other systems could definitely take note of the way WP handles plugins.

Post reply on HN