Live data from Hacker News

WordPress has left the building

kevinjohngallagher.com

71–80 of 223 posts

Re: WordPress has left the building

#71
post #48

Earlier quoted context omitted.

A few years ago i recommended website baker as a nice simple CMS, which is also hackable if necessary. That was three years ago. Maybe the situation has changed, but i would never recommend a complexity-monster like Typo3. Typo3 is "enterprisy" in the negative sense. http://www.websitebaker2.org

Don't be too hard on TYPO3, it has its virtues. For instance, it has the most elegant handling of multilingual content I've ever found in fifteen years of working with CMSes. But for a small single-language site (i.e. 99% of the sites people develop) it's definitely overkill.

For as complex as it is, TYPO3 is pretty usable. I built a site on TYPO3 before I ever messed with WordPress some 6 years ago. Now that I think of it, I'd probably opt for TYPO3 before Drupal.

Re: WordPress has left the building

#73
post #4

What's the alternative?

We're working hard at building the best fully hosted one at http://www.webpop.com

Our aim is to get close to the power of something like Drupal with a simple and usable interface that's a joy to use. All fully hosted, requiring no maintenance.

We're the only hosted system that is also truly extendible (you can build extensions in server-side javascript) and we're seeing both tiny one-pages and large content driven pages being built with our product by now.

Re: WordPress has left the building

#74

Wait so he's complaining that a free piece of software that is designed to "create a beautiful website or blog" (from Wordpress.org) doesn't cut it as a high powered CMS? I think if we're honest, wordpress is a blogging platform and if you try to deform it into your own little niche needs, you need to accept the inherent risks.

The post mentions that the issues extend into WordPress' regular redesigns of the admin interface, and their consistent lack of solid testing: "This would actually be a much smaller issue if it wasn’t for the WordPress’ update schedule. I am 100% for constant updating of software, but the current desire to redesign the AdminUI 2-3 times a year creates a huge amount of friction from both clients and developers." "Kev,…

That portion of the post is the opposite of what I'd pick out to illustrate that it has a point. It's just dripping with misplaced rage and entitlement and doesn't even point out a bug in any shipping version of WordPress. It strongly emphasizes the word "BETA" and then goes on to literally curse them out for the fact that it had major bugs. Like, yeah, that's what that means. Do you go grabbing a cook's half-done risotto and tell them to quit because the consistency is terrible?

I agree that WordPress's issues multiply in proportion to how much you want it to do, but the fact that prerelease software has bugs is not one of them.

Re: WordPress has left the building

#77
I disagree with most of the content. WordPress is a great CMS and it can be used for it. I do advanced projects and it fits fine. The list of his hard truths isn't that hard. Some of them are just rare cases that most people even irritate at.

The Admin UI doesn't get a redesign 2-3 times a year. There is a big difference between redesign and adjusting. Most of the buttons are still on the same place as in WordPress 2.8. They only got replaced or have different colors. Maybe they should create admin themes so you have the ability to hold down some versions.

I think he and his team should stop complaining about things where they never tried to make it better. At least it doesn't stand in that post. I do think that WordPress can and should do a better job and I am do help a little bit with it. That was something they should do to.

The complaint about a Beta product is just lame. It's a beta version. What can you expect. A lot of Beta version of other software do break things.

This is just my point of view. If you dive into WordPress Core files you can find solution for problems you thought WordPress couldn't handle. Sometimes it can be little bit ugly code tho.

Re: WordPress has left the building

#78
post #74

Earlier quoted context omitted.

The post mentions that the issues extend into WordPress' regular redesigns of the admin interface, and their consistent lack of solid testing: "This would actually be a much smaller issue if it wasn’t for the WordPress’ update schedule. I am 100% for constant updating of software, but the current desire to redesign the AdminUI 2-3 times a year creates a huge amount of friction from both clients and developers." "Kev,…

That portion of the post is the opposite of what I'd pick out to illustrate that it has a point. It's just dripping with misplaced rage and entitlement and doesn't even point out a bug in any shipping version of WordPress. It strongly emphasizes the word "BETA" and then goes on to literally curse them out for the fact that it had major bugs. Like, yeah, that's what that means. Do you go grabbing a cook's half-done ri…

"... the fact that it had major bugs. Like, yeah, that's what that means."

No, that's not what beta means. I expect core functionality to work properly in a beta. I expect there to be intermittent issues, and I expect advanced/fringe features to maybe sometimes not work. I expect there to be workarounds for most (but not all) issues that crop up. But the freakin' main menu didn't work. How is that beta-quality? I'd hesitate to call it alpha-quality.

And yes, I know, it's open source, it's free, you shouldn't feel entitled. I know. I wrote and maintained open source software for 5 years. But c'mon, from the perspective of the developer, have enough pride in your work to at least do a little testing before throwing a release over the fence.

Re: WordPress has left the building

#79
i stopped reading immediately when i saw CMS. you're using the wrong tool, that's it, don't cut your feet to fit in your favorite shoe. and save your time(and ours) to write this, it's just the wrong tool for CMS, and it's not wordpress's fault!
Post reply on HN