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

61–69 of 69 posts

Re: WordPress 3.5 “Elvin” Released

#61

Post by brass9 »

zalew wrote: post #13
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…

>> 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.

That's because twig was originally created by Armin - the creator of jinja. It was part of a (now abandoned) blogging engine called chyrp. Later, twig was salvaged by Fabien and incorporated into symfony.

Re: WordPress 3.5 “Elvin” Released

#62

Post by rmccue »

mildweed wrote: post #45
chrisblackwell wrote: post #14

WordPress could really change their bad reputation by dropping support for PHP 5.2 in the next release, and requiring 5.3. 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.

Wordpress has adopted the PDO standard. It will be in WP 3.6. http://core.trac.wordpress.org/ticket/21663

That's the aim. Whether we actually get land it in 3.6 or not is another issue, since 5.5 isn't stable yet, so it's not really an issue just yet.

(Personally, I want it, but I can see there being friction, given the possibility of breakage.)

Re: WordPress 3.5 “Elvin” Released

#63

Post by rmccue »

Otto42 wrote: post #42
chrisblackwell wrote: post #14

WordPress could really change their bad reputation by dropping support for PHP 5.2 in the next release, and requiring 5.3. 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.

Somehow I doubt that we'll decide to drop support for 65.5% of our users (roughly 26 million websites). http://wordpress.org/about/stats/

It's funny how many people say WP should drop 5.2 compatibility. It's certainly possible to push the hosts towards using 5.3, but the fact is that the user base simply isn't there yet.

Re: WordPress 3.5 “Elvin” Released

#64

Post by rmccue »

dave1010uk wrote: post #3

Does anyone know if / when WordPress may start using a modern PHP framework (eg zf2 / symfony2)?

Despite what other people are saying, it is quite possible that we'll be taking parts of Symfony: http://core.trac.wordpress.org/ticket/22325

At the moment, we're not considering dropping support for PHP 5.2, so we'll likely take the best ideas and implementation from various frameworks and combine them. I'm fairly committed to reiterating wherever possible that WP isn't a silo and we need to be looking at what other PHP projects are doing. We're getting better at that.

Re: WordPress 3.5 “Elvin” Released

#65

Post by mars »

intelliot wrote: post #47
cooperadymas wrote: post #15

Earlier quoted context omitted.

Saying there's little competition is a huge stretch. WordPress is the dominant force by a large margin. But from small static site generators, hosted platforms, other open source alternatives, to enterprise-ready solutions there are a lot of competitors hitting nearly every segment of the market. http://trends.builtwith.com/cms provides some good trends of the big players, but I wouldn't put too much stock in it. Tha…

> 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. Honest question: Can you name one? I'm seriously looking for a WordPress alternative, but I haven't found one that is truly BETTER.

depending on what type of project you are building you might want to have a look at yeager (http://www.yeager.cm). although the site states beta, the tool is stable and used in live environments since several years.

Re: WordPress 3.5 “Elvin” Released

#66

Post by cooperadymas »

eclipticplane wrote: post #58
cooperadymas wrote: post #53

Earlier quoted context omitted.

What I mean by this is others have a better structured, more solid & easily extendable code base, better separation between presentation and logic, etc.. Obviously, this is somewhat of an opinion, and it only refers to the underlying structure. For the end user, WordPress is probably the best. A large part of this is due to its ecosystem of plugins and themes. You shouldn't need to build custom code on top of WordPre…

Isn't MoveableType in Perl?

Possibly - I've never done anything with it. The PHP statement was really only for the first two, sorry for the confusion!

Re: WordPress 3.5 “Elvin” Released

#67

Post by Otto42 »

DigitalSea wrote: post #48

The media changes are a welcome addition, but I can't help but feel Wordpress is still lacking in the media department quite a lot. One feature I've been hoping for in terms of media management is folders to organise media instead of paginating pages of all images being displayed which usually involves duplicates being displayed. I love Wordpress, but it would be great to be able to upload specific images for example…

Re: media, one step at a time. :)

Re: custom fields: This makes little to no sense to be in core, because custom fields are just that, "custom". There's no point in giving the end user the ability to make their own meta boxes hooked to custom post meta if there is no plugin or theme actually using that meta data. Creating a meta box is something that the theme/plugin should do, because it's actually going to use the data gained from that meta box.

In other words, the horse goes in front of the cart, not the other way 'round.

Re: WordPress 3.5 “Elvin” Released

#68

Post by BUGHUNTER »

Unfortunately there is still no reliable unattended upgrade process inluding rollback (aka migration) for wordpress. I looked into this a little bit, but there does not seem to be a reliable way to check if plugins have been executed successfully and with expected results or not, so you never know after an upgrade if your site is broken.

There are still many other issues with the code, but having a clearly defined error-handling / -signaling for plugins would be the one single change that would help in many problem areas of wordpress development - making rules and knowledge about successful plugin execution and error handling obligatory for plugin devs could be the one single change that could also help to reduce that annoying flood of unbelievable bad code to be found in WP plugins repo.

Post reply on HN