Turning Wordpress Into a Framework With MTV

Re:Turning Wordpress Into a Framework With MTV by rmrk on Wednesday October 19, 2011 @02:36PM (#3131430)

Because WordPress is great, but it's a pain to do extensive development with.

Replicating WordPress functionality in Rails or Django would be an enormous job. Making WordPress more like Django was much less work.

[ Parent | on HN ]

Re:Turning Wordpress Into a Framework With MTV by Otto42 on Wednesday October 19, 2011 @03:52PM (#3131760)

Gotta say that I don't get it either. They've basically just added yet-another-HTML-templating system into the mix. Question not answered: "For the love of all that is holy, why?"

PHP is an HTML templating system. Tacking on yet another one strikes me as more than a little pointless.

[ Parent | on HN ]

Re:Turning Wordpress Into a Framework With MTV by stdbrouw on Wednesday October 19, 2011 @03:57PM (#3131783)

"All the HTML is in one place and contains as little code as possible.

One place for code that interacts with data.

One place for code that processes requests and responses.

One place for all the URL regexes.

And all these places are predictable."

[ Parent | on HN ]

Re:Turning Wordpress Into a Framework With MTV by Otto42 on Wednesday October 19, 2011 @04:16PM (#3131861)

So, when you have a problem with the system, then to find the bug you have to look in three or four places instead of one.

[ Parent | on HN ]

Re:Turning Wordpress Into a Framework With MTV by superchink on Wednesday October 19, 2011 @07:36PM (#3132652)

By that reasoning, we should just code a whole site in a single PHP page that handles both the backend processing and the display layer and generation of HTML.

It's not about decreasing the number of files (to look into to find bugs), it's about organizing the code into logical pieces that are more manageable.

[ Parent | on HN ]