3 ms·
The problem is that while that while static page generation is definitely the best fit for what most people need, it is not the best fit for what they think the
by smacktoward 13y ago
The problem is that while that while static page generation is definitely the best fit for what most people need, it is not the best fit for what they think they need. One of the big reasons WordPress was able to dethrone Movable Type as the #1 blog software was precisely because of its dynamic pages -- that was a big point of attraction for people over MT's static page generation approach. So much so that Movable Type's developers eventually felt the need to graft a half-baked dynamic page system onto their product, just so they could tell people who wanted dynamic pages that they shouldn't rule out MT altogether. (It didn't help in the end, but the fact that they felt they had to do it at all speaks volumes.)
Why do they think they need dynamic pages? The upsides of dynamic pages (no more waiting for pages to rebuild) are right there in their face, while the downsides (your server falling over if you get more than three readers at a time) don't become evident for a while. So to non-technical folks, dynamic pages seems like a no-brainer. They don't learn the downsides until they leap up and bite them.
This mismatch between what people think they want and what they actually really should want based on their needs is sadly quite common in tech products, and explains how a lot of crappy products managed to become more popular than a techie would ever have expected them to be.