I love WordPress so much!
Nonetheless, I wish a few things could be included as a feature for the WordPress core and for the requirements of theme and plugin developers. Hopefully, some of my WordPress wishlist gets back to WordPress, or theme and plugin developers.
Please let jQuery die already.
I try to avoid jQuery at all costs. I even specify that I want the Vanilla Javascript solutions when I ask for help on Stack Overflow. I am probably going to write a blog post about how much I prefer using Vanilla Javascript or other modern frameworks, but here is a very short list of reasons I avoid jQuery.
- Performance Overhead: While jQuery simplifies development, it comes with a performance trade-off. The library adds an additional layer of abstraction, resulting in a slight performance overhead compared to native JavaScript solutions.
- Large File Size: The full version of jQuery can be relatively large in file size, especially when compared to newer, lightweight libraries and frameworks. This can impact page load times, particularly on mobile devices or areas with slow internet connections.
- Frameworks offer more efficient and scalable solutions for building complex single-page applications.
Not to mention that multiple theme and plugin developers either come with the jQuery bloated library or make requests to the library via CDN. So please, WordPress developers, let jQuery die already. – Added May 16, 2023
Use Namespaces
Many issues with compatibility come from using the same naming conventions. Namespaces are the best way to prevent many bugs—more info. about Namespaces – Added December 16, 2023
Enqueueing files on the WordPress core level
Every theme and plugin should include an “Enqueue File” where the WordPress Core can read it and display on the dashboard which themes or plugins have enqueued certain APIs. The theme or plugin developers would enqueue an API by using an if statement.
So if you have a theme that enqueues the Google Fonts, then when you install a plugin that also has the Google Fonts enqueued in its “Enqueue File,” then the if statement would allow or deny the enqueue action, and you would get a warning in the dashboard that there is a theme or plugin already enqueueing it.
Enqueueing files on the theme and plugin level
Alternatively, and probably a better way to implement it is to have a WordPress “Enqueue File” in its core where all themes and plugins would reference their if statement.
- Google Maps
- Google Fonts
- Font Awesome
- Bootstrap
- etc.
Of course, there will also be issues with versioning, but there are a lot of smart people at Automattic who could work out all of the nuances. – Added December 15, 2023
I will continue to add to my wishlist, so be sure to come back and checkout this list.
