4 ms·
The bitching is because I have to support their crap. Along with the wordpress security hole of the day lottery, I have to deal with php (and it's cruft and se
by x0x0 12y ago
The bitching is because I have to support their crap. Along with the wordpress security hole of the day lottery, I have to deal with php (and it's cruft and security holes), plus wordpress constantly spamming you with "new version" with zero indication of whether it's just another code dump likely to break plugins or if it fixes zero days, yet still likely to break plugins.
Happiness skyrocketed with octopress.
edit: competent devs would issue long term releases with only security fixes backported. As it is, getting a set of plugins plus a theme working is fine, but it then requires ongoing maintenance because wordpress constantly internally churns and breakage regularly occurs, partly due to their apparently ill-specced internal api. I presume they don't do this either because of lack of engineering ability or because they want to drive people to their hosted product. Either way, it's not a good product.
- mindctrl-org 12y agoYou can legitimately argue about the legacy code base, but the bit about regular breakage is total bullshit.
- x0x0 12y agoNope, it's my experience (and a brief google will tell you the same). Feel free to clamp your hands over your eyes and sing la-la-la to suit yourself, though. ps -- if you google why wordpress doesn't issue stable releases, it's because it's too hard. Which rather demonstrates the quality of people working on wordpress, I think, given real developers manage to do it for whole OSes, which are a tad more complicated than a cms [1] [1] http://wordpress.org/support/topic/long-term-support http://wordpress.org/support/topic/long-term-support
- georgestephanis 12y agoSo then Chrome is a stupid hacky browser because it doesn't ship a long-term-support version, and just expects everyone to update?