It's true that it will lead to healthier wrists and more productivity, but thats not the point. I know people with incredibly unergonomic setups and habits (vscode with membrane keyboard and a chronic overuse of the mouse) that get around the same or more actual features implemented as me. There might even be something to be said for more friction forcing you to think more.
The reason most of us do it (at least if we are honest with ourselves) is because it's fun---and that's ok. Jumping around in vim on a split keyboard gives me the same joy that watching my first lines of code execute in Gamemaker Studio 2 did in 8th grade.
It's always worth investing to make your work joyful.
Claude 3.7 Sonnet is much more restrained and does smaller changes.
I also worked on Android Wear's iOS app for working with iPhones.
The major problem I see now with these excuses, that I'd like to claim wasn't an issue when I was making them circa 2015-2017, is they're cargo cult (a la Apple likes making things that just work) or boogeymen (if they did anything different, a bluetooth connection would be used, unencrypted, sending all your data into the ether).
The watch has been out for 10 years.
Software is software. Where there's a will, there's a way.
It's very, very, very, hard to believe there's 0 way for Apple to ensure an encrypted connection.
Put another way, avoiding the global observations: If it's impossible, why allow watches to be paired at all?
If you didn't know you could see the massive progress both projects have made in web compatibility here: https://wpt.fyi/results/?label=master&product=chrome&product...
As of today, browsers pass this percent of tests:
Chrome: 96.82%
Firefox: 95.41%
Safari: 94.97%
Ladybird: 89.30%
Servo: 78.61%
Also Linux issue pointer: https://github.com/fastrepl/hyprnote/issues/67#issuecomment-...
Anyway, thanks for your work and good luck!