> Root cause is Catalina regression that fails keyboard inputs when a UIKeyCommand is registered for the same key. UIResponder chain regression most likely.

Sure there is... The app would capture those as shortcuts instead of as user input. You know...exactly what's happening here. If this interferes with writing tweets also then that should be easy to figure out.

As I said above, I'm not saying it's not because of the regression but it's more likely to me that Twitter messed it up. Otherwise, why is no other app experiencing this issue if it was done "according to the docs".

Well, like you say, it's not common to use shortcut keys without modifiers right? So it doesn't seem that surprising to me that nobody noticed the regression.

https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41...

As Linus Torvalds would say, "WE DO NOT BREAK USERSPACE!"

But there are also some UI fails on Twitter's side here too - like clearing the password field after clicking Show Password and typing more, and preventing arrow key navigation within the field.

— https://forums.macrumors.com/threads/catalina-causing-issues...

Yes which is exactly why I think it's likely he's being disingenuous about the root cause of this. Shortcut keys typically need modifier keys and, even in the instance where they don't, there has to be some check from the app to determine whether an input field or the main window has focus.

To be clear, I'm not saying it's 100% certain that this isn't an Apple issue but, based on Twitter's track record with their apps, this likely is on Twitter.

https://twitter.com/nolanobrien/status/1189623346033381376?s...

I know Windows has had various UI frameworks come and go over the years, but they're all fundamentally layers on top of the underlying stable Win32. For Mac I'd not really dug into how to write GUIs, but I know there's things like Carbon, Cocoa, etc., and those seem to be the base itself, and change significantly or are even entirely removed at the whim of Apple. Is there any stable GUI API on the Mac at all?

There's also this, which is frankly quite terrifying: https://news.ycombinator.com/item?id=11638367

[1] https://news.ycombinator.com/item?id=21174947

Note that the open source releases often get things scrubbed or ifdef'd out of them.

> There's also this, which is frankly quite terrifying

I fail to see your point.

I mean things like TODO comments, not deliberate censorship.

I fail to see your point.

You don't notice anything wrong with the insane complexity to do almost nothing? A similar near-nothing app would be 1/10th the size on Windows, if not smaller.

Using a C++ library from C is not hard because objects map to structures in a straightforward manner (and in fact early C++ compilers were C++ to C translators), and you would need to use structures anyway, unless the library was obtusely designed with nonessential complexity. That's how the Win32 API works too (with the exception of the bloated COM stuff.)