Ignoring the fragmentation of course; although that seems to be getting less and less each year (so long as you ignore Safari).

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.

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.

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.

For now

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.

ExternalUser: Hello here is a calendar invite I would like you to attend, please confirm or deny

User: Thank you, now I can verify the request and choose to add this to my calendar or not

Also the biggest bottleneck is honestly the web browser itself. It _technically_ works, but it's super stripped down and JS-heavy sites especially struggle.

I'm not denying that there's "plasticized paper" in the box, but as far as I could tell, it was 100% recyclable. As for "breaking down the box", if you flip the lid around to the bottom of the box, and then stack them together, then it saves a good bit of space. But yes the moulded cardboard that held the laptop itself was a pain to get out of the bottom section.

Also, when multiple people are working on the same code, it's nice that they all are forced to spell things the same way...

Most users either don't have such strong opinions about their scroll bars, or would prefer it looks coherent with the application, or OS-native (your preference). But I can almost guarantee the larger group of non-technical users will have never thought about the styling of their scrollbars for more than a few seconds.

Also in terms of accessibility, so long as they're doing CSS-only changes, and the bar is sized compliant and has proper focus states, assistive technology won't care.

HL:Alyx got close to the "only in VR" sort of mechanics, but change 2-3 big set pieces, and it could very much be done on a 2D screen.

Simply search for 8,6,7,5 and you should find it.