alt Hacker NewsI couldn't reproduce the Color Picker bug mentioned at the end.
Just one small thing to add about the Color Picker: I think it's a good example of how native UI apps have changed over the last decade.
The macOS Color Picker is nice. The idea is to have a single color picker for the whole system. It's extensible, so apps can add their own custom pickers (for example, an OKLCH picker), and you can reuse your palettes across applications.
Sounds great! But most of the applications where you might care about those features (customization, sharing your color schemes, etc.) don't work with the native Color Picker: Figma, Adobe apps, all Electron-based apps, and so on. So the Color Picker's features are useless. That component of the system is exactly the same as it was when I got my first Mac in 2007.
There are multiple nice native features that apps don't use; over time, they become forgotten and barely maintained.
I don't know what the solution is, but at some point, I think Apple should take frameworks like Tauri or Electron into account and build integrations for developers who use them. I know the integrations exists (they are the native APIs), and it's the developers' responsibility to use them, but that's not happening, and it ends up affecting the UX.
> build integrations for developers who use them.
in practice, developers will not use them. they think they have better ideas and they don't care about platform or the user as an abstraction over the platform. they could use the existing thing.
it's the same mindset that has automakers not wanting to support CarPlay. they think they can do it better or just as well and it's completely missing the point: the user doesn't want to fuck with their custom one-off UI.