5 ms·

> the dependency on PHP can turn many developers away from using it That's interesting, as most people claim PHP and the army of developers that come with it,

> the dependency on PHP can turn many developers away from using it That's interesting, as most people claim PHP and the army of developers that come with it, is a major factor in WP's domination of the CMS market. If WP had initially been developed in Python, perl or anything not named PHP would it be the dominating force it is today? (Honest question, I don't presume to have the answer) I'm a PHP developer, I hate working with WP but this whole article had me scratching my head asking "what? why?". This isn't 'fixing' wordpress, the author is essentially building a spec for a new/different CMS that isn't dependant on WP. There's lots of those not named Wordpress.

redwall_hp 11y ago
>If WP had initially been developed in Python, perl or anything not named PHP would it be the dominating force it is today? Most of the solutions around at the time were perl, including Movable Type, which was the WordPress of the time. The only reason anyone went with WordPress was because the MT developers jacked the price up, and WordPress was free at the right place/time.
- pp19dd 11y ago
  MT was fairly clumsy in some ways by comparison to WP, though my use of the word is very questionable. Updating templates was always a pain because we'd want to update a sidebar widget, and it would take hours to have that change reflected (regenerate all pages statically) because we had a legion of prolific writers and they churned out tons of content throughout the years. By comparison, WP was dynamic - change instantly reflected. Of course, that difference had its disadvantages - you had to make sure WP traffic didn't melt the server(s), optimize for the traffic, then finally give up on caching strategies after traffic growth overwhelms conditions, and upgrade to a CDN to basically imitate a static site you were avoiding. In some ways, we're making a full circle in blogging technology (and web in general), but here's a major WP disadvantage at this moment in time: it might take 32MB of ram to generate a 3kB page.

redwall_hp 11y ago

>If WP had initially been developed in Python, perl or anything not named PHP would it be the dominating force it is today? Most of the solutions around at the time were perl, including Movable Type, which was the WordPress of the time. The only reason anyone went with WordPress was because the MT developers jacked the price up, and WordPress was free at the right place/time.

pp19dd 11y ago
MT was fairly clumsy in some ways by comparison to WP, though my use of the word is very questionable. Updating templates was always a pain because we'd want to update a sidebar widget, and it would take hours to have that change reflected (regenerate all pages statically) because we had a legion of prolific writers and they churned out tons of content throughout the years. By comparison, WP was dynamic - change instantly reflected. Of course, that difference had its disadvantages - you had to make sure WP traffic didn't melt the server(s), optimize for the traffic, then finally give up on caching strategies after traffic growth overwhelms conditions, and upgrade to a CDN to basically imitate a static site you were avoiding. In some ways, we're making a full circle in blogging technology (and web in general), but here's a major WP disadvantage at this moment in time: it might take 32MB of ram to generate a 3kB page.