I’ve noticed something like this while playing the game Hollow Knight: Silksong. Most of the time when I was trying to beat a difficult boss, I wasn’t trying to beat it while it’s hard and would take a lot of effort. Instead I was working on making beating the boss easy (which was hard). So typically by the time I would beat a boss, it did feel like comparatively little effort was being expended.
> Now consider humanity after full automation. Instead of millions of migrant workers, humanity will have trillions of digital laborers at its disposal.
One piece in the logic I don't get is this: why would (or should) the earnings done by those workers go into the pockets of humanity, who isn't doing the work, rather than into the pockets of the laborers, whether digital or not?
Or more likely just the companies themselves if all the labor is AI no? Seems like the society/economy will need stringently enforced policies to even begin to think about making this happen
Glad to see that unlike last time with the M4 release, this time they released M5 in more devices than just the iPad Pro at the same time. That said, there’s still room for improvement: the MacBook Air and Mac mini weren’t updated yet.
A random recent example off the top of my head: view photos in AVIF format. It does work in Photos app, but not in Preview app nor in Messages app somehow. At least this the case on iOS 26 and so I suspect iPadOS 26 too. It works on macOS 26.
Edit: I realize that ordinary people might not yet care about exporting to AVIF, but they may receive such photos from other people.
It's a very nicely crafted article. It was quite jarring to see a box containing the following text:
> If you open this on a computer instead, you will have a chance to play with some emulators!
Instead of what? I was under the impression that the device I was on is a computer.
Edit: I was curious to understand what caused the site to show that box. From looking at the source and some interacting in the console, it seems to have been due to the 'isiOS' variable having the value 'true'. It was true despite the device not running iOS because '(navigator.maxTouchPoints && navigator.maxTouchPoints > 2)' was truthy, and window.MSStream wasn't. This device, a Surface Pro X, or more precisely the Chrome 139 browser running on it, reports 10 max touch points and doesn't have MSStream defined, and that appears to have been enough for it to be mistaken as a not-a-computer.
By now, after refreshing, I see an extra sentence 'Hey, site, you got it wrong. This is a real computer!' Perhaps the author saw this comment and added it quite quicky? If so, thank you!
It's a helpful link, thank you. I think I need to play with toolchain more. Last time I checked I think there was some corner case that was not covered but I could be wrong.
I see that I can change it with a command like `go env -w GOTOOLCHAIN=go1.21.1+auto` but then again I'm doing something I don't want, managing the version.
reply