This is some old draft article that I didn’t want to trash, so I’ll try to at least partially salvage it.
I played a bit with Deno deploy a while back, and I must say quite impressive that using Deno deploy is very easy to fast spawn a serverless worker, similar to a Cloudflare worker.
If I were to deploy something on a large scale where serverless workers could be a suitable environment as a replacement for a different backend set-up, and I had to choose a paid service, I would probably go with Cloudflare only because it allows the worker to be written in several languages, and thus gives you better flexibility. View full article
For those who like to implement both light and dark themes and want to do that in the most optimized way I have good news for you Google Recently implemented in Chrome > 93 the ability to get the user preference using server-side technologies.
Why is that important? Because just in case you didn’t hear the term FART by now it stands for “Flash of inAccurate coloR Theme”, the main issue is that if you don’t know the user preference before sending a response to a request, you can optimally set the user preferred theme.
After a dreaded existence, AMP probably will fade away after June 2021, if I were to predict I’ll say it will stick around for a couple of years but its usage will decrease dramatically, and that because Google will not treat AMP preferentially anymore. That’s mostly because the new June update of the Google search engine will take into account the performance of every website and since AMP was made in order to create lightweight websites.
I never really hated AMP, though from what I’ve seen on Reddit mostly AMP was one of the most hated technologies and it was a bit funny to see so many complain, personally I even contributed to AMP source to the worker-dom / amp-script, added the
scrollIntoView, and I also have in the pipeline the refactored implementation for
onbeforeunload, that maybe will get merged too when the maintainer will come back to the office. View full article
If you want to load the post faster you can use JS to fetch your post, but on modern browsers probably preloading pages will be faster, the only drawback of preloading is that you’ll consume storage for your visitors even if they don’t visit the preloaded links, also with preloading links you will consume more bandwidth and resources on the server-side.
So if you want to stick with fetching with JS here is an example, but first, as a note, the example will not use the default REST API mostly because the default API only returns the content title and other attributes of the post and, we want to add things like Yoast data(without making two API request) also, in this case, will transfer some of the article template surrounding the content. View full article