Counterpoint: is the web browser not already fulfilling the "universal app engine" need? It can already run on most end user devices where people do most other things. IoT/Edge devices don't count here, but this day most of their data is just being sent back to a server which is accessible via some web interface.
Ignoring the fragmentation of course; although that seems to be getting less and less each year (so long as you ignore Safari).
I'm curious how often you find factual inaccuracies in the LLM responses when doing that.
I've found that more often than not, it gets at least one key feature/option/etc. outright wrong whenever I've tried that, making it effectively useless for me. Since I need to verify the exact information myself anyways, I'm 90% the easy to just having the different items in comparing up in side-by-side browser tabs, anyways.
Prior hosting provider was a little-known company with decent enough track record, but because they employed humans, stuff would break. When it did break, C-suite would panic about how much revenue is lost, etc.
The number of outages was "reasonable" to anyone who understood the technical side, but non-technical would complain for weeks after an outage about how we're always down, "well BigServiceX doesn't break ever, why do we?", and again lost revenue.
Now on Azure/Cloudflare, we go down when everyone else does, but C-Suite goes "oh it's not just us, and it's out of our control? Okay let us know when it fixes itself."
A great lesson in optics and perception, for our junior team members.
This format is unreadable on mobile, it keeps opening up my keyboard and scrolling up a bit when it does.
I understand and appreciate the "why" of the format, but this also could have been a non-editable "editor-like" presentation and achieved the same result.
The problem with any tool like this is that people are often _terrible_ at knowing how to clearly explain what it is they want/what their actual issue is.
Key example: "login is broken!" Could be the captcha didn't load, captcha was blocked by their ad blocker, they are rate limited, they used the wrong email, they used the wrong password, they don't have an account, they aren't on the right website, etc.
Turnstile is the in-page captcha option, which you're right, does affect page load. But they force a defer on the loading of that JS as best they can.
Also, turnstile is a Proof of Work check, and is meant to slow down & verify would-be attack vectors. Turnstile should only be used on things like Login, email change, "place order", etc.