> ...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?

> … The Congress shall have Power . . . To declare War, grant Letters of Marque and Reprisal, and make Rules concerning Captures on Land and Water;

Can’t say I’ve seen this?

> as if an actual state of war exists

"as if"

So, because congress didn't declare it, the war doesn't exist? Lmao

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.

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?

My main issues with ghostty: the global shortcut for quick window suddenly stops working and works again only if I focus ghostty. (On a mac)

The other one is quick window goes out of the monitor if i have disconnected and connected the laptop from minitor.

Another: sometimes autocomplete suggestions are shown incorrectly in some weird location (like middle of the screen, not at the cursor), again occasionally.

I actually fixed one cause of this, which is released in 1.4.0.

https://github.com/ghostty-org/ghostty/pull/12714

The only other cause I've encountered is if a secure input (password) field is focused, since macOS won't give apps global keyboard events for obvious reasons. If you focus a normal text input, it should start working again.

I have noticed where macOS doesn't properly release its reference to a Secure Input properly. I've documented how to determine if this is the cause here: https://github.com/ghostty-org/ghostty/issues/11883#issuecom...

This is such an annoying quirk of macOS, I regularly SSH to some servers I need to get my password to from 1Password, and I am apparently incapable of re-programming myself to copy the password prior to starting the SSH connection, so what happens is I SSH, open 1Password quick access (which dismisses my Ghostty-adrum quick-terminal), copy my password, and then frantically spam my quick-terminal shortcut until I remember it's blocked because macOS has decided its not allowed in the current state.

Would be great if we could opt out a few pre-determined key combinations from this system, but I guess that's never happening.

Thanks so much for maintaining Ghostty tabbed quick-terminal by the way, you're a legend <3

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

I'm happy with ghostty now too, but until a couple months ago it didn't have search. Which made me uncertain how people use terminals without built-in search. It really surprised me that it apparently was so low on the must-haves list that it took over a year to have it. I think I search terminals multiple times a day when I'm operating production systems.

AFAICT, the bug from 1.3.1 where you cannot paste into the search field is still present in 1.4. I guess agents doing all the grepping these days?

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

IIRC they announced they've done a bunch of improvements to the integrated terminal in the release notes for the current or previous bigger release. But it was not switching over to libgbostty. The linked blog post says "starting from version 2026.3" which is the current EAP release. The post is only two days old.

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.

Even the shortcut keys were the same everywhere!

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

I think Omni Group requires an Omni account login to use any or most of their apps.

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.

Yes? That was true even of the first iPad.

It’s definitely not true even now. Even a moderately fast finger drag will lag noticeably - usually by at least a frame in even very carefully tuned situations. It’s just physics. If you aren’t noticing it, you’re just used to it.

Try rapidly dragging up and down to scroll a web page.

For some people, it’s motion sickness inducing of it gets too laggy

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

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

I also don't care how if things _look_ native, I care if the work like a native app. For example, on the rare occasions I touch Windows, I expect standard keyboard shortcuts to work. On macOS, I expect full integration with the accessibility frameworks and OS affordances like services.

A lowest common denominator idea of "everywhere" is just not that useful.

How do you handle this for your own software? Could you please link me to one of your project's websites and install instructions? What specifically do you find that one OS has that's mandatory for a good/native UIs that others don't?

I hear you on the native UI is better all things considered. I'm trying to figure out how that works in practice. I.e., to accompany a "cross-platform UIs are inferior to native ones", you would be effective to also include the workflows you use. In a realm where you choose options, eliminating one should come with illuminating another, as one must choose a path, and others could be eliminated for their drawbacks as well, leaving none available. What is your path here?

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.