This old fart is happy to keep on bopping to new music such as the Brownswood (Merci Gilles) backed Swindle, here with Kojey Radical;
Here are some more numbers for that memorable day;
- Most popular pages:
- Do not donate: 10 013
- Homepage/ archives: 1 108
- about:futtta: 235
- Hacker News 7 978
- Facebook 112
- Search Engines 84
- Outgoing links:
- https://en.wikipedia.org/wiki/Flanders 959
- https://en.wikipedia.org/wiki/List_of_countries_by_inequality-adjusted_HDI#List 809
- https://profiles.wordpress.org/futtta 596
- https://www.kiva.org 87
And my server? Even at the busiest time (around 10-11 AM UTC+1) it quietly hummed along with a 0.11 system load :-)
On Facebook someone asked me how to do Gutenberg the right way to avoid loading too much JS on the frontend, this is a somewhat better organized version of my answer;
I’m not a Gutenberg specialist (for from it, really) but:
- the wrong way is adding JS with wp-block/ wp-element and other gutenberg dependencies on init calling wp_enqueue_script,
- the right way is either hooking into enqueue_block_editor_assets (see https://jasonyingling.me/enqueueing-scripts-and-styles-for-gutenberg-blocks/)
- or when using init doing wp_register_script and then register_block_type referring to the correct editor_script previously registered (see https://wordpress.org/gutenberg/handbook/designers-developers/developers/tutorials/block-tutorial/writing-your-first-block-type/).
I’ve tried both of these on a “bad” plugin and can confirm both solutions do prevent those needless wp-includes/js/dist/* JS-files from being added on the front-end.
wp-includes/js/dist on the frontend due to plugins doing it wrong.
So dear plugin-developer-friends; when adding Gutenberg blocks please differentiate between editor access and visitor access, only enqueue JS/ CSS if needed to display your blocks and when registering for front-end please please frigging please don’t declare
wp-element, … and all of those other editor goodies as dependencies unless your 100% sure this is needed (which will almost never be the case).
The performance optimization crowd will thank you for being considerate and -more likely- will curse you if you are not!
Autoptimize 2.5 is almost ready! It features a new “Images”-tab to house all Image optimization options, including support for lazy-loading images and WebP (the only next-gen image format that really matters, no?);
Live version of a great new song by a new (super-)band by one not-so-new (Conor Oberst) and (given her age) one newish artist (Phoebe Bridgers). Somewhat reminds me of the alternative rock-scene of the nineties (Hole, Throwing Muses and whatnot) and that is a good thing!