Hacker News new | comments | show | ask | jobs | submit login

I'd almost like to see it go the other way. WordPress is a good blog, but a poor CMS choice for anything but the most basic of websites. I reckon the "66%" that use WordPress use it for personal sites or very small business sites (1-10 visitors a day) on shared hosting. There are huge sites using it, but they seem to be the exception that proves the rule.

I cannot see why people use WordPress over the likes of Concrete5 or a full CMS on any other platform outside of WordPress being accessible for entry-level developers. For this reason, a full rewrite of WordPress to be solely a basic CMS would probably have these novice developers flock to the system, allowing WordPress to scale back down to doing what it does best.

>I cannot see why people use WordPress over the likes of Concrete5 or a full CMS on any other platform outside of WordPress being accessible for entry-level developers.

I run a very modestly profitable website that gets about 1k visitors per day. I'm not even an "entry-level developer", I'm not a developer at all, with only the most rudimentary ability to kludge together a little JS and php.

I chose Wordpress for the site, even though it's not a blog. In fact, creating a system where posts weren't displayed in chronological order actually took a few hours of blindly hacking at various WP functions.

The reasons I chose Wordpress over an existing CMS:

* I already know how to use WP

* There is a vast array of FLOSS themes and plugins to meet virtually any need available

* Wordpress is well supported by shared hosting and managed VPS providers (through cpanel etc.)

* It's relatively easy to get free high-level support through IRC because so many people know WP

Most of these reasons are inertia based. It would be a vast undertaking to create a CMS version of Wordpress that actually gained traction because, awkward as WP is, it has an enormous library of free existing solutions to take on virtually any problem. This quality, which the author of the article complains about, it the same reason WP would be so hard to kill. Even if your product is better for a given purpose, people aren't going to give up the advantages of WP I outlined above just for an incremental improvement in UX or speed.

Because it's easy to develop for, can scale to be one of the top ten sites on the internet, and your users won't need training to use it.

Now I'll be the first to tell people there are certain things that you should build from scratch, but the examples of what people build with WordPress can be pretty breathtaking even to me:


Many other CMS's are easy to develop for. The "scalability" issue is true but as I'm aware none of the top ten sites use WordPress.

The point I disagree with the most is that users won't need training to use it. I hear this all the time with absolutely nothing to back it up, other than "I haven't trained a user to use it".

Well, I have, and the users for this company struggled a lot with how things will work. I've trained users on numerous scripts, including Umbraco, Sitecore, Concrete5 and bespoke CMS's and every one of the others were far easier to both sell to a client and train. Umbraco and Concrete5 are far better for users than WordPress.

Which top 10 site is running on wordpress? And how much of it is static content being served by a cache and completely avoiding wordpress at all?

Fair question: WordPress.com. This list from Quantcast has WP.com at #16


But that only includes *.wordpress.com subdomains, and our highest traffic blogs almost always invest the money to have their own domain. We have a tag[0] to track those in Quantcast, and it's currently at 129.7M people in the US, which would place it between Facebook (143M) and MSN (98M). (Blogger might have a similar boost into the top 10, but I don't see any others in the top 50 that could have so many mapped domains.)

Of course we cache, with a publicly available WP plugin called Batcache.[1]

[0] http://cl.ly/image/081G1r2f0Z18 [1] http://wordpress.org/extend/plugins/batcache/

So, none of them? It doesn't include other domains and it shouldn't include other domains. Really, it is being exceedingly generous in that estimation already. Hosting thousands of totally independent, small sites is trivial, and does not require scaling wordpress in any significant way. Facebook is one site, all their data needs to be able to be accessed by all their software. Bob's blog and Joe's blog are totally independent, and have no need to be on the same software or hardware at all. Thus making scaling a non-issue.

I agree that using caching is normal, but the difference is the total reliance on caching. I wouldn't be impressed with google's scalability either if it were 99.9999% static pages being served up.

That's sort of like saying Facebook scaling is a "non-issue" because it's just a bunch of small, independent profile pages. Of course some elements can and should be sharded, but that doesn't mean that scaling is trivial, especially as you get into more advanced and social features and a rapidly increasing percentage of traffic is logged in and fully dynamic.

I think we agree that "scaling" small (sub-RAM-size) amounts of data to a largely logged-out and cached audience is easy, but I think you think of WordPress.com as much smaller and more static than it actually is. My apologies if I'm misunderstanding your point of view.

If you want to see standalone sites in the top 100 running WP besides wordpress.com, check out time.com, umbrellanews.com, celebuzz.com, and large sections of nytimes.com, cnn.com, and people.com. If you were to spider the top million Alexa domains, you'd find about 17% of them on WP:


Except that as I pointed out, facebook isn't independent pages. Wordpress.com is tons of tiny, entirely independent sites. That's like claiming godaddy is a top 10 website because they host tons of little PHP sites. Tons of little sites is not the same as one big site.

I realize lots of people run wordpress. That doesn't support the claim that it easily scales to the traffic demands of a top 10 site.

That's incorrect. WordPress.com serves hundreds of thousands of websites from a single install. That means one set of PHP files and one database. Not unlike Facebook.

It is entirely correct. First of all, they do not serve hundreds of thousands in one install. Second, it doesn't matter. The point is they are individual sites, they are not tied to each other in any way. So lets say they host 100 sites on server X. Now one of those sites explodes in popularity and the server can't handle it all. They can simply move the site to its own server (or a server shared with a smaller number of other sites). It doesn't matter that the data is currently in the same database, as the data is in no way tied to the data of the other sites in that database. So it can be trivially exported and moved to a different server.

I run a Wordpress blog hosted on a Micro EC2 instance capable of handling dozens of thousands of visitors every day.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact