jen20

> before that it was formally verified

Jepsen is a fantastic tool - and one every database engineering team should have in their arsenal - but it proves the presence of bugs, not the absence of them. It is not formal verification, just a more rigorous form of existential testing.

The phrase was first recorded as used in the London press in the late 1700s. It’s well understood across the English-speaking world. The fact that you might not have heard it before (or are being deliberately obtuse about the pretty obvious meaning) doesn’t change that.

> ...the operational and economic condition in which a nation, military force, or organization mobilizes its resources, industries, and policies as if an actual state of war exists...

Yes?

That’s exactly what guardrails must be if they are to be useful or trustworthy. Deterministic, enforceable and impenetrable.

I think you're likely attributing too much competence to the kind of place that restricts outbound traffic to 80 and 443 in the first place.

Aha, this explains why I've never seen this kind of thing: I don't use quick window!

I used iTerm and iTerm 2 for almost 20 years before switching to Ghostty full time in 2024 with minimal fuss besides the muscle memory of "cmd+space ite" switching to "cmd+space gho" to launch it!

Do you have specific examples of usability issues?

Aha, I wondered why the JetBrains terminals had become so much better recently. Didn't realize they'd made the switch.

I haven't experienced that, but bought all of their products I use via the Mac App Store. I imagine they need some kind of activation if you download them from elsewhere.

XP was particularly hideous in the default fisher-price configuration, but Windows 2000 was the peak of Windows UI.

As for inconsistent - what!? Every app looked approximately the same, and behaved in a predictable manner.

IA Writer, IA Presenter, everything from Omni Group, Acorn, Procreate, Capo, Sketch.

Yes? That was true even of the first iPad.

No - almost all of the software I work on is at least one of:

- proprietary,

- command line tooling,

- single-platform.

A good example of what I consider to be a great approach (not mine) is Ghostty, which has fully native UI per platform and a shared core between platforms. JetBrains tools also go out of their way to integrate with platform conventions everywhere.

An example that cross-platform toolkits usually get wrong: cursor navigation in text fields. Home and End do different things on different platforms, and on macOS, basic emacs/readline bindings are supposed to work in all text entry fields.

It’s worth noting that this extends beyond GUIs - command line tools written in Go tend to use “package flag” which is native nowhere. The standards between Windows (which has two, in cmd and powershell), GNU-style and “legacy” Unix style are just not reconcilable without implementing platform-specific behaviour.

> It's pretty sad that Google, Microsoft, Nvidia, Sequoia etc.....

Three of those four are public companies, so the public can absolutely participate.