4 ms·

I might be in the minority on HN, but I think that WordPress is doing fine just as it is. Whereas my gag reflex kicks in at the mention of a Drupal contract, W

I might be in the minority on HN, but I think that WordPress is doing fine just as it is. Whereas my gag reflex kicks in at the mention of a Drupal contract, WordPress is still pleasant-ish to work with. It's simple enough that I can get my own custom work done without having to spend a ton of time fighting the core system. Though, YMMV depending on the nature of the custom application, I'm sure.

runn1ng 14y ago
I think it's the perfect example of "worse is better" approach. Yes, it might not be perfect, but it does well what it says it does, it's quite simple to customize and you just upload it online and you are set. Being nice internally is good. Being working with tons of available plugins is better.
- mgkimsal 14y ago
  I mostly agree, except it's not "simple to customize" in even a majority of cases. The 'upload and online', however, is and will continue to be the killer feature that will keep rails/python/java/etc-based CMS at a major disadvantage. Starting projects today, I prefer Grails. Starting a project which I had an intention of distributing to a wide number of users (potentially for eventual world domination), I'd use PHP. Nothing else comes close to the ease of getting the widest number of people able to upload/install.
deleted 14y ago
[deleted]
kvnn 14y ago
I agree that WordPress is fine just as it is. I love that everything custom must go into wp-content. I love that any custom theme functions are supposed to go in functions.php. This keeps things easy to isolate and debug. Its an extreme whose opposite is Drupal, where some obscure functionality can be popping off in one of hundreds of .module or .tpl files. Its pretty much summed up by "my gag reflex kicks in at the mention of a Drupal contract, WordPress is still pleasant-ish to work with".
- chc 14y ago
  I think "more pleasant to work with than Drupal" is the new "better than a kick in the teeth."

runn1ng 14y ago

I think it's the perfect example of "worse is better" approach. Yes, it might not be perfect, but it does well what it says it does, it's quite simple to customize and you just upload it online and you are set. Being nice internally is good. Being working with tons of available plugins is better.

mgkimsal 14y ago
I mostly agree, except it's not "simple to customize" in even a majority of cases. The 'upload and online', however, is and will continue to be the killer feature that will keep rails/python/java/etc-based CMS at a major disadvantage. Starting projects today, I prefer Grails. Starting a project which I had an intention of distributing to a wide number of users (potentially for eventual world domination), I'd use PHP. Nothing else comes close to the ease of getting the widest number of people able to upload/install.

deleted 14y ago

[deleted]

kvnn 14y ago

I agree that WordPress is fine just as it is. I love that everything custom must go into wp-content. I love that any custom theme functions are supposed to go in functions.php. This keeps things easy to isolate and debug. Its an extreme whose opposite is Drupal, where some obscure functionality can be popping off in one of hundreds of .module or .tpl files. Its pretty much summed up by "my gag reflex kicks in at the mention of a Drupal contract, WordPress is still pleasant-ish to work with".

chc 14y ago
I think "more pleasant to work with than Drupal" is the new "better than a kick in the teeth."