Why Should We Never Make a Change to WordPress Core or Plugins?

In the world of software development, change is always afoot. Developers are constantly working to update and improve existing software, and to create new ones.

Unfortunately, this constant flux can lead to instability and inconsistency in the software ecosystem.

The WordPress ecosystem is no exception to this rule. As the official platform for blogging and content management for over 30 million websites, WordPress is constantly being updated and improved.

However, this same dynamism can also lead to instability and inconsistency in the WordPress core and plugins.

For example, consider the recent controversy surrounding the removal of the wp_ajax_nonce() function from the WordPress core. This function was used to prevent Cross-Site Request Forgery (CSRF) attacks.

However, many WordPress users were unhappy with the decision to remove the function, arguing that it was essential for maintaining a robust blog platform.

In the end, it was decided that the wp_ajax_nonce() function would be removed from the WordPress core. But this decision led to a slew of plugin updates that were suddenly incompatible with the new WordPress core.

This inconsistency led to widespread chaos and confusion among WordPress users.

This is just one example of the inherent instability and inconsistency that can result from changes to the WordPress core. It is important to remember that core WordPress updates are always tentative, and that plugins should always be tested before they are updated.

Ultimately, it is always best to stick to the established norms and conventions of the WordPress ecosystem. This will help to ensure stability and consistency in the software ecosystem, and will make it easier for users to understand and navigate the platform.