WP Tavern › Forums › Create Topic
alex As it should. This conversation (and a few others recently) are showing that wordpress development seems to be diverging from user need, and that is never a good thing. Mark’s attitude on this one is to me a summary of the problem: “we know better, do it our way or else”. This new content sharing is certainly valid for SOME wordpress installs, but for others it’s the worst possible thing: More code that can go wrong to add functionality that they aren’t interested in. That Mark (and core developers in general) seem unable to grasp that Wordpress is not being used only in one way makes it very hard to have the discussion at all. The results? More plug in bloat, as we are required to add ANOTHER plug in to disable core features that aren’t really core. Wouldn’t this functionality be better as a plugin, rather than as a force? The discussion of HTML static pages is a pretty common one. Many sites are not very dynamic, updating weekly, monthly, or even almost never (in the case of corporate image sites). Converting the output of wordpress into static pages lowers the overhead required to generate those pages for each viewer. Yes, caching would help, yes, there are plug ins for that, but some prefer to avoid the security risks and the system load inherent in running Wordpress to generate a site that isn’t changing very quickly. Which brings up for me the final point: page caching and reduction of system load is something that would be great for even basic users. Lowering the overhead to run wordpress would seem to be a very good, very core concept. Yet, all of that functionality is in a plug in. Instead, we get emojis, a comment system which appears to be intentionally shackled, and other “core” improvements that aren’t improving things for everyone. Why should these things be outside of the core, but not emojis? Yes, it’s enough to make you very sad indeed.
alex
As it should. This conversation (and a few others recently) are showing that wordpress development seems to be diverging from user need, and that is never a good thing.
Mark’s attitude on this one is to me a summary of the problem: “we know better, do it our way or else”. This new content sharing is certainly valid for SOME wordpress installs, but for others it’s the worst possible thing: More code that can go wrong to add functionality that they aren’t interested in. That Mark (and core developers in general) seem unable to grasp that Wordpress is not being used only in one way makes it very hard to have the discussion at all.
The results? More plug in bloat, as we are required to add ANOTHER plug in to disable core features that aren’t really core. Wouldn’t this functionality be better as a plugin, rather than as a force?
The discussion of HTML static pages is a pretty common one. Many sites are not very dynamic, updating weekly, monthly, or even almost never (in the case of corporate image sites). Converting the output of wordpress into static pages lowers the overhead required to generate those pages for each viewer. Yes, caching would help, yes, there are plug ins for that, but some prefer to avoid the security risks and the system load inherent in running Wordpress to generate a site that isn’t changing very quickly.
Which brings up for me the final point: page caching and reduction of system load is something that would be great for even basic users. Lowering the overhead to run wordpress would seem to be a very good, very core concept. Yet, all of that functionality is in a plug in. Instead, we get emojis, a comment system which appears to be intentionally shackled, and other “core” improvements that aren’t improving things for everyone. Why should these things be outside of the core, but not emojis?
Yes, it’s enough to make you very sad indeed.
Name *
Email *
Website:
Topic Title (Maximum Length: 80):
Forum: — No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Email Address
Submit
Enter the destination URL
Or link to existing content
