Colors and color names are culture dependent, and you are not guaranteed that people in different cultures agree on what color something is.
The most famous of these discrepancies is Japan and green vs blue, or why does Jenkins by default use red, yellow and blue instead of red, yellow and green.
So I would urge using something other than colors as an example of shared human experience.
You should steel-man the argument. GP is talking about qualia, obviously for the sake of the argument you assume the comparison is between two people with similar eyes.
The steel men (armored enemy knights) are exactly the inverse of the straw man (training dummy) metaphor. I think it's a fantastic term since it directly addresses the point (tackle the best opposing arguments head on instead of a poor subset/facsimile of them), it fits within the existing straw man metaphor, it's terse, and it's very clear.
> The colors of traffic lights can be difficult for red–green color-blind people. This difficulty includes distinguishing red/amber lights from sodium street lamps, distinguishing green lights (closer to cyan) from white lights, and distinguishing red from amber lights, especially when there are no positional clues (see image).
> All but one admitted to difficulties with traffic signals, one admitted to a previously undeclared accident due to his colour blindness, and all but one offered suggestions for improving signal recognition. Nearly all reported confusion with street and signal lights, and confusion between the red and amber signals was common.
The wild success of traffic lights comes from having 3 colors at fixed positions. You put those 3 colors in a single color changing light and I would assume the accident rate would measurably increase.
I don’t mind Liquid Glass either to be honest. I kind of like it even. I also completely agree regarding software quality, which is abysmal (I am sufficiently aware of the internals of a lot of things on macOS to know most of the time why it’s like this, but it’s still unacceptable).
Mostly the failing events (e.g. the Messages app failing to keep the first word of a message when typing rapidly after sending a message) are, I think, due to Apple using Catalyst for these apps.
Catalyst was an ambitious project, which works… mostly. But in the details, it has a lot of rough cuts. I fully expect Apple to end up rewriting Messages and co completely in SwiftUI eventually, but that will take many years, if they ever do it.
For the rest, most of the time my wild guess would be that Apple is constantly migrating their frameworks, or creating new ones, and the engineers developing apps are using ever moving frameworks. The framework stabilizes at the end of the release cycle (or sometimes even later…), which leaves no time for the front devs to truly finish quality control on their part.
Basically, to summarize, the release cycle is too small. Apple should do releases every two years instead of every year. Or drop the cycle altogether and just release when ready.
Completely unrelated, but what’s with the spaces inside the parenthesis here? It’s super weird (and leads to incorrect text layout with a standalone parenthesis at the end or beginning of a line…)
Not really… using js to change the CSS on the go is not a good practice. Why does it matter? Because of the “dark mode” browser extensions. They often use the presence of @media query (or other standard CSS means of setting dark mode colors), and if it’s the JS that changes the colors we often get partial Dark Mode, which does not work at all.
No. It does not. It does not understand anything. Stop anthropomorphizing bots!
reply