3 ms·
This is arguably what's so dangerous about a plugin ecosystem in general. On the one hand, you can quickly implement a bunch of useful new functionality at the
by CM30 3y ago
This is arguably what's so dangerous about a plugin ecosystem in general. On the one hand, you can quickly implement a bunch of useful new functionality at the drop of a hat, and that's obviously incredibly useful for non technical folks.
But at the same time, you then often end up dependency hell, and realise that any changes going forward will break something or another that your site depends on, leading to many, many sleepless nights. God help you if you're one of those folks who installed hundreds of plugins, because an upgrade often meant 'revert everything to default, then hope at least some of your plugins had equivalents for the next version'.
It's why I'd recommend anyone who can do so to only use their own code for a WordPress (or other CMS based) site, and keep the third party stuff to popular plugins you know will get regular updates.