most web sites still don't work from most trains in 2024

At the risk of bending a term, one wants transactions over the web to be "as atomic as possible".  You know what I mean.

Say for something like a payment: 

Client and server line everything up, then "wam commit with tiny data", "bam commit worked with tiny data b", and with proper feedback to user at each stage.

What actually happens is that devtards create a sprawling, heavy mess with all sorts of back-and-forth.  It pulls in garbage from all directions.  When it's on a perfect internet connection, such as the devtard's dev box, it just about works, most of the time.  That's the level they get it to.  If there is the slightest connection glitch, packet loss, slowness, it just sort of fizzles out in undefined ways.  Maybe the thinger spins round for ever, or something just remains greyed out or doesn't load.  Occasionally some sort of error message will be produced.

A payment or other online transaction should work with a 9600 bps connection with significant packet loss.  Yet most things fail on much better connections than that, such as the ones on train, whether train wifi, or your own mobile device and personal hotspot / router.

Below are screenshots from the at least 3 failed attempts to buy an Interrail ticket during a train journey from Southampton to Oxford.  All failed in time-consuming ways, and I had still not succeeded in buying the ticket by the end of the journey.

It is hard to imagine an example of greater collective failure than the so-called "Internet".

Given the fact no one reads my blog, and the low limit on this card, there's not much point scribbling out the card details.