I see this problem almost every year with macOS updates. Here are two examples that I recall of the top of my head. They are already a few years old but really annoyed me, because I spent the time to write detailed bug reports, kept re-testing the issue, and in the end Apple shipped the bugs and never fixed them:
- use of some custom NSTextAttachmentCells was broken when they added force touch dictionary lookup to NSTextView. As far as I know it was never fixed. The API is still documented and if you use it it will cause crashes as soon as someone uses force touch in a text view.
- fat binaries (32/64) stopped working when the 32bit binary uses Objective C garbage collection even when running on a 64bit system and the 64bit binary does not use garbage collection. This is clearly an error, Apple did not care about it. The only way to make such an app launchable again on 64bit is to remove the 32bit binary (that wouldn't run on a 64bit machine anyway)
Nah, back in those days PCs even had a RESET button. So even when it was trivial to turn it off and on again, there was still a designated button to restart the computer.
Not the ones we had at my school and home in the 80s. Nor the outdated DOS machine I inherited to write school essays on when my dad got a new Dell with Windows 95. Just a power button or switch, depending on the model.
Getting a loan from a bank would be cheaper than subscription pricing.
There are two reasons to use subscription pricing:
1) Price discrimination: You want to charge a large customer more for the same device
2) Lowering the capital expenditure by hiding the true price in operating costs
You could argue that (1) is good for small clinics, because they get access to the same machines as big clinics for a smaller cost. But I believe it's just a way to remove opportunities for competitors and results in everyone paying higher prices, even smaller clinics.
The kind of HIIT I'm doing is only 10-20s bursts, to stay within ATP-PCr energy metabolism (little lactic acid production). A short sprint followed by 2 minutes rest. That's hard to achieve with a treadmill.
It will make me as wary as I am around people that wear those little AI notetaker/recorders, so, very. At least with those it's a single use device that you can spot, now any Apple Watch could be listening, fun!
I don't know if this will be the common reaction, but after seeing this I've made a mental note to not discuss anything private with anyone wearing an Apple Watch. Makes me suspicious of iPhones, too, after years of defending them and saying that 'technology is always listening' is a silly conspiracy
“Always listening” in the way people have been conspiratorially claiming your phone is listening to show you ads is silly.
Always listening in that the owner could run an application that could be recording them and you on the other hand has been a possibility since pretty much day one.
As much as I hate to say it, the most accurate GPS in a watch is the new Pixel Watch from Google, and its accuracy comes from uploading the GPS signal to Google to do building-aware post processing using Google’s database of worldwide buildings to solve the multi-path issue, plus DGNSS. Simply having dual frequency isn’t enough when you run on the streets of New York City. With Google’s solution, it can even detect which side of the sidewalk you are on while running.
I’m just not aware of any method that can do this without uploading your data to the cloud.
There's the Japanese approach of deploying a dense cluster of satellites above one geographical area (QZSS), but of course that only works in the areas those satellites are above.
reply