4 ms·

Everything's great, but their text editor still can't accept markdown by default.

by capex 13y ago

jacques_chester 13y ago
Shipping caching by default would be a better start. The Wordpress team have said that the hosting implications of writing to disk make it a non-starter; but for some reason that didn't stop them from shipping auto-update or one-click plugin/theme installation in mainline.
- Viper007Bond 13y ago
  The WordPress leads speak from experience. Caching objects to disk was introduced in WordPress 2.0, released in 2005. Turns out it actually slowed down the vast majority of sites. Databases are really, really good at storing and retrieving data, much more than filesystems, especially when those filesystems are often remotely mounted drives. The functionality was pulled back out of WordPress in a later version, leaving all of the various hooks needed for a plugin to super-easily implement it on its own. I use a memcached powered one for example.
  - jacques_chester 13y ago
    Firstly, MySQL is actually terrible at the core task of Wordpress, which is joining tables with TEXT fields. If it finds a TEXT field it throws its hands in the air and joins on disk, taking great care to avoid any indexes you might have added to speed up those joins. Any time the query cache isn't there to save you, you wind up stomping around on disk anyway. Fun fact: the recent comments widget that ships in mainline blows the query cache. Secondly, file caching could still ship in mainline with a tickbox to enable it. Thirdly, I've never seen a site that wasn't improved by file caching. However I believe you that the Wordpress guys get a lot more reports than I do. Finally, 2005 was eight years ago.
rmccue 13y ago
This is exactly what plugins are for. Most people aren't going to need this, and for those that do, there's a tonne of plugins out there that will add this functionality for you.

4 ms·

Everything's great, but their text editor still can't accept markdown by default.

by capex 13y ago

Everything's great, but their text editor still can't accept markdown by default.

jacques_chester 13y ago
Shipping caching by default would be a better start. The Wordpress team have said that the hosting implications of writing to disk make it a non-starter; but for some reason that didn't stop them from shipping auto-update or one-click plugin/theme installation in mainline.
- Viper007Bond 13y ago
  The WordPress leads speak from experience. Caching objects to disk was introduced in WordPress 2.0, released in 2005. Turns out it actually slowed down the vast majority of sites. Databases are really, really good at storing and retrieving data, much more than filesystems, especially when those filesystems are often remotely mounted drives. The functionality was pulled back out of WordPress in a later version, leaving all of the various hooks needed for a plugin to super-easily implement it on its own. I use a memcached powered one for example.
  - jacques_chester 13y ago
    Firstly, MySQL is actually terrible at the core task of Wordpress, which is joining tables with TEXT fields. If it finds a TEXT field it throws its hands in the air and joins on disk, taking great care to avoid any indexes you might have added to speed up those joins. Any time the query cache isn't there to save you, you wind up stomping around on disk anyway. Fun fact: the recent comments widget that ships in mainline blows the query cache. Secondly, file caching could still ship in mainline with a tickbox to enable it. Thirdly, I've never seen a site that wasn't improved by file caching. However I believe you that the Wordpress guys get a lot more reports than I do. Finally, 2005 was eight years ago.
rmccue 13y ago
This is exactly what plugins are for. Most people aren't going to need this, and for those that do, there's a tonne of plugins out there that will add this functionality for you.