I ran into this exact issue trying to board a flight from the USA to Tokyo, a number of years ago. About 2 steps from getting on the plane a plain clothes cop pulled me aside and searched my luggage. The only thing he asked about, repeatedly, was if I was carrying cash. Fortunately for me, I was not. After he made sure to go through everything I had he let me get on the plane.
When the only thing he was concerned about is if I had any cash on me, it sure felt like an attempted robbery. He never asked about drugs or anything else illegal I might have had.
Definitely this. It would be great if HTMX has a similar path to jQuery, where the browsers adopt enough of the features as native that it is no longer required.
This could spiral into some interesting combinations. Imagine Redbean with PHP support, and it already includes SQLite. You could keep your entire site: PHP, database, files - in one file that also runs your web server, and it works on multiple operating systems.
This. Call it MPA Foundation, or something. With an MPA foundation there are plenty of opportunities to make easy improvements to performance and page experience, while still having all of the page features work without JavaScript.
Not because there are tons of users running around with JS turned off, but because every page load is running without JS until the JS finishes executing successfully ( as noted by many others ).
I've long thought about this as the 15 minute rule. Meaning, with curl, reading the docs/examples, and 15 minutes I should be able to get a response back from you API.
I've recently started using yadm, which is a light abstraction on top of git. One big reason - "Alternate Files" support - which makes it easy to have MacOS and Linux binaries for the same tools, along with the rest of my shell setup, in one Git repo.
Why do people think AMP is faster? Pre-caching by Google.
This is a huge part of it. It is not unusual for an HTML page to load faster than an AMP version when loaded directly by a browser ( render blocking on the 3rd party amp JS bits can result in it taking longer to start rendering ).
The part that often allows AMP to win is that Google caches it to their own CDN and Chrome will pre-fetch it from there. What is interesting about that is that none of that has anything directly to do with format/spec of AMP pages.