3,441 karma · joined February 10, 2020
Instead of just swapping out the registry, try baking it into your machine image.
I haven’t dabbled with hackintoshes in nearly a decade, I stepped away around the time iMessage started needing those extensive hacks to work. Things seemed to shift away from driver/bootloader gaps to faking Apple hardware. Years earlier, I had an Asus Eee PC (remember “netbooks”?) that ran macOS without any major issues. I even built a machine that I believed I could hackintosh easily, though it never quite worked as well as I hoped.
The era of random companies selling pre-built Hackintoshes was so cool. Kids these days probably wouldn’t even believe it if you told them, like how Netflix used to actually send you a DVD in the mail. :)
For several years, there's been an issue with audio message recording in iMessage. Prior to iOS 26, it would silently fail; the recording would "begin" but no audio would be captured. This would happen 3, 4, even 5 times in a row before it would actually record audio.
Apple is clearly aware of the issue, because in iOS 26 the failure is no longer silent. Now, you'll get feedback that "Recording isn't available right now". Yet the incidence is...exactly the same. You might have to try 5 times before you're actually able to record a message.
It's simply infuriating, and it makes no sense to a user why this would be happening. Apple owns the entire stack, down to the hardware. Just fix the fucking bug!
Does the Go team have a natural language bot or is this just comment.contains(“backport”) type stuff?
In 2023 they had $11.4 million in revenue, almost entirely donations, and spent about $6 million. They had about $10 million in assets.
The problem with this approach is you need a certain number of guinea pigs on the bleeding edge or the outcome is the same (just delayed). There is no way for anyone involved to ensure that balance is maintained. Reducing your surface area is a much more effective strategy.
I don’t think the icon situation is enough to keep me off the release, but agree that the design is just kind of a mess and not my taste.
I wouldn’t count on it.
My experience has been that the cost of “patching” is often bugs and instability, having gained nothing security-wise.
You could avoid it by leaving “name” and just adding the additional fields. Maybe that’s the “right” thing to do if you have a ton of consumers and spotty test coverage. But if there’s a lot of fragile code out there (parsing “name” in subtlety different ways, etc.) it’ll never be fixed/improved. Things can get gnarly over time because there’s multiple ways to do something, and everything starts to feel like “legacy code”.
I tend to think that for private codebases, it’s important for breaking changes to be easy.
They….did not. Maybe the sharp edges eroded into smoother curves, and the nerve acclimated so any sensitivity resolved, but your teeth did not “heal” as in “replace the lost portion”.
I use the swipe feature because I guess I have wide fingertips and frequently hit unintended, adjacent keys when pecking on the keyboard (especially as I’ve gotten older). The words produced by swiping often make no grammatical sense, and are frequently esoteric words that I just can’t believe rank high enough on a basic frequency list to suggest. Not to mention my own vocabulary, which apparently is not considered by the keyboard at all.
I had a way better experience using SwiftKey on my android phone 15 years ago.