6 ms·
>It struck me recently how this list of plugins I saw in the 2023 Annual WordPress Survey wasn’t full of fun and interesting plugins that do interesting and uni
by coldtea 3y ago
>It struck me recently how this list of plugins I saw in the 2023 Annual WordPress Survey wasn’t full of fun and interesting plugins that do interesting and unique things, they mostly just fix boring problems that users shouldn’t even be worried about having to fix at all.
The word the author is looking for is "useful". The plugins are useful instead of exciting. When it comes to plugins to a CMS I'd have the former, thanks...
- hnbad 3y agoI think his point is more that most of them solve issues the CMS should address directly (in his opinion) or that should be better addressed outside the CMS (e.g. SSL and caching). The emphasis in that sentence is in the last part: > they mostly just fix boring problems that users shouldn’t even be worried about having to fix at all And I agree, to an extent: import/export should probably be rolled into core, comment spam shouldn't be the default (although arguably this just means comments should be removed from core), technical SEO should be covered by the CMS and editor (be that Gutenberg or Elementor) and WordPress should have a built-in way to handle forms and configuring e-mail sending.
- coldtea 3y ago>they mostly just fix boring problems that users shouldn’t even be worried about having to fix at all Because the problems they want to fix aren't the problems I want to fix. I don't want to send emails with Wordpress, or do polls, or whatever. If we add the superset of features to the core Wordpress it would be a 1GB install, with a team of 100000 needed to maintain it. It's not as if it's not already one of the most full featured CMS as it is, or can be used for tons of things without anything else out of the box, from a personal or business blog, to a full featured publication with multiple authors. >import/export should probably be rolled into core The core does have import/export. >comment spam shouldn't be the default (although arguably this just means comments should be removed from core) Not having comments in the core would be controversial to say the least. Not to mention against the TFA complain ("not enough stuff in the core"). >technical SEO should be covered by the CMS It is, for the most part. The rest is SEO snakeoil the third-party plugins cover. >WordPress should have a built-in way to handle forms and configuring e-mail sending. Are forms and email the role of a CMS?
- hnbad 3y agoYour tone and your conflation of what I said with what I cited the author as saying suggests you hold very strong opinions on this and you're only looking for someone to argue with, not an argument, so I'll refrain from further engagement.
- coldtea 3y agoYour answer appears like you want to bring psychological ad-hominems about tone and personal motives to this because you don't have a counter-argument, so I gladly accept you refraining from further engagement... I also didn't conflate "what you said with what [you] cited the author as saying". As your quoting was meant as an endorsement of that argument, I responded to it. When you quote an argument you want to highlight from an article, expect people to comment on that.
- hnbad 3y agoI didn't say your opinion is wrong, I said I'm unwilling to engage with it because of how you are expressing it. That may be "ad hominem" but not an "argumentum ad hominem" because there is no argumentum. I didn't say your argument is invalid because you're abrasive, I said I'm unwilling to argue with you because you are abrasive, regardless of whether you're wrong or not. Ironically, inferring that I'm trying to insult your characters or misrepresent your motives "because [I] don't have a counter-argument" is an "argumentum ad hominem". Your first comment stated that the author was wrong to expect "exciting" plugins because the plugins he laments the existence of are "useful". I cited the author to clarify that his complaint was that the plugins are only useful because of limitations of the CMS core. I agree with the author that some of those limitations should be addressed by the CMS rather than being left to plugins. Fine. Let's look at what you actually said: > the problems they want to fix aren't the problems I want to fix This seems tangential. What you or I or the author wants is probably not a useful metric for what should be a feature. The author's argument seems to be that if these are the most widely used plugins and they exist to augment or expand on existing functionality, that should be done in core so the plugins don't need to exist. You can disagree with arguing based on popularity but "I don't need it" is not a productive argument. > I don't want to send emails with Wordpress This implies Wordpress doesn't normally send emails. However Wordpress core has plenty of places where it sends emails (or tries to, often barely succeeding because it uses the built-in functionality of PHP which usually ends up in junk filters). Even changing the admin email address involves a confirmation email. I can see an argument that being able to provide an email SaaS backend should be a plugin but SMTP seems like a reasonable option if sending emails is part of Wordpress core's standard behavior. > [I don't want to] do polls I didn't say polls, I said forms, as did the author. Most websites have forms, usually at least a contact form. I'd wager more Wordpress websites have contact forms than comments and yet comments are enabled by default. > The core does have import/export. And yet the Wordpress Importer exists as an official plugin and is one of the most widely installed. If the functionality is important enough to have in core and the plugin is popular enough to be this widely installed, that sounds like the core functionality should be extended instead of having a plugin. > Not having comments in the core would be controversial to say the least. Yes, which is why I don't see it being removed. But they should probably not be enabled by default if they're prone to spam and it would be less controversial to move them out into a plugin once they're no longer enabled by default. > Not to mention against the TFA complain ("not enough stuff in the core"). The complaint isn't "not enough stuff in the core" but "vital stuff missing in the core". It's not about adding "more stuff" but about extending what is there with what people are clearly missing. > If we add the superset of features to the core Wordpress it would be a 1GB install, with a team of 100000 needed to maintain it. That is a slippery slope argument and catastrophizing based on conjecture. You don't define "the superset" but it seems to include more than the author or I listed as things that should probably be handled in core. > [Technical SEO] is [covered by the CMS], for the most part. The rest is SEO snakeoil the third-party plugins cover. The author acknowledges the snakeoil part, however the plugins do add some things that aren't covered by the CMS. It seems reasonable to add functionality like being able to provide OpenGraph meta data to core, no? > Are forms and email the role of a CMS? Clearly Wordpress is not "a CMS", it's Wordpress. Are comments the role of a CMS? Arguably forms are more integral to "a CMS" than comments and comments are just a special case for it. And as I described above, sending emails is indeed integral to Wordpress so setting a proper transport for them seems like core functionality.
- creshal 3y agoSending emails, setting proper meta tags, creating forms, not having security vulnerabilities, undoing broken upgrades, caching, … are all features that a fully-featured, bloated CMS like Wordpress really shouldn't need plugins for. It'd make sense if WP had a "small core, versatile APIs" philosophy, but that flew out of the window over a decades ago; it's extremely bloated these days and has tons of features, yet the basics are still missing.
- coldtea 3y ago>Sending emails, setting proper meta tags, creating forms, not having security vulnerabilities, undoing broken upgrades, caching, … are all features that a fully-featured, bloated CMS like Wordpress really shouldn't need plugins for. You could say the same thing about Emacs. Wordpress provides the infrastructure. It doesn't have to provide everything and the kitchen sink.
- creshal 3y agoPlease read the second paragraph, too. Wordpress hasn't been about providing "infrastructure" (what does that even mean, when essentials are missing?) for a decade at least.
- coldtea 3y agoIt means "building blocks" to build different kinds of websites: blogs, brochure sites, personal website, business site, magazine style, portal style, and so on. You can then add plugins for the missing functionality. Also, what essentials" are missing? I've deployed it with 0 third party plugins (at most I've add Jetpack) several times, with no issues. So? Or do you mean "your essentials" which could be different than mine? I could not give a rat arse about BS "SEO" plugins for example, basically selling snakeoil to suckers, as if anybody ever got even a nudge above in Google rankings because of those...