macOS 15 vs macOS 26 mouse cursors.
The info.plist files accompanying the macOS cursors are interesting. They have the shadow values (shadows are drawn at runtime and not included in the cursor PDFs). They’re also full of rounding errors, which makes me thing they were generated by a tool. A human probably typed 0.033 and 0.45, and rounding errors caused the issue in the screenshot.
@marcedwards Don’t think those are rounding errors, just an effect of the way that floats are represented in binary. So a human indeed probably entered the values you said, but these representations easily parse to the right binary representation that is closest to that number.
@eelco Sure. By “rounding errors” I meant float to string conversion for the JSON, or anything related. It’s clear the JSON wasn’t human authored.

@marcedwards Try this in the terminal:
> echo '{"test":0.45}' > test.plist
> plutil -convert xml1 test.plist
> cat test.plist

As you can see, the way floats are stored in the XML serialization has nothing to do with how artisanal the original JSON was.

Bonus points: edit the XML version back to 0.45 and run the convert command again.

@eelco Nice! Not entirely sure what you’re saying though. You’re saying 0.45 can’t actually be represented as a double, right? https://www.binaryconvert.com/result_double.html?decimal=048046052053

My comment was that the JSON was authored by a tool, not a human.

Double (IEEE754 Double precision 64-bit)

Online binary converter. Supports all types of variables, including single and double precision IEEE754 numbers

@marcedwards Yes correct. My reaction was to your initial statements:

“They’re also full of rounding errors, which makes me thing they were generated by a tool.”

Not errors, and yes plist files are not intended to be hand authored and will generally go through a check / formatting step.

“A human probably typed 0.033 and 0.45, and rounding errors caused the issue in the screenshot.”

This is not true because they are not errors / issues.

Apologies for being a reply-guy! 🙈

@eelco All good! I didn’t choose the best way to describe it. Is there a better phrase? “Impossible values to be represented by a double” is probably better? I guess the value was still rounded to the closest it can be, so… that is a rounding error of sorts? You may know this, but there’s float to string conversion libraries that don’t have this issue.
@marcedwards What are the `delay` and `frames` here?
@mrudokas That’s for the “busybutclickable” cursor that has an animated spinner.
@marcedwards mostly okay, except for the basic cursor that’s not shown here and the hands, those are downgrades for sure…
@manolo Yeah, the hands are worse. I feel like the hands could be simpler and a bit like the macOS 26 ones, but they just haven’t landed on a good design yet. I like the new standard cursor. It’s very jarring to change it after all this time though.
@marcedwards WHERE IS MY MICKEY MOUSE HAND 😔
@marcedwards I personally really like all of these new ones. They're both more cohesive, and more legible.
(i.e. no small holes in the four-way arrow, no wispy thin end to the curved arrow, much better legibility of the left/right drag arrows. even the magnifying glass doesn't have an awkward mix of line widths anymore)
Probably I also just like the aesthetic of it!
@Cykelero @marcedwards Exactly my thoughts as well! These are great and reasonable polishes to the icons without changing them too much
@chechoribero @Cykelero Yep, there’s quite a few clear improvements. The hands need work though. I like the new standard cursor (not shown in my image).
@marcedwards I think all are improvements except the hands.
@marcedwards I’m not mad at any of the changes except those Windows ass hand icons
@deandmx Yep! I genuinely like most of the changes, and I’m okay with the hands being simplified, but… they don’t look good as is.
@marcedwards Not sure if playful is the right word, look at those boring white hands 😭