Robert Ryan

@robertryan
54 Followers
71 Following
140 Posts

I’m not a fan of the iPadOS “Smart Activation” feature for focus modes. I prefer to manually control when and if I need different focus modes. However, my iPad keeps prompting me every few days to turn this feature on.

I gather that this is a known issue. I’ve already provided feedback to Apple, but has anyone found a workaround to stop this persistent prompt?

This is the first app that I’ve actually deleted just because the icon was so bad; an assault on my visual senses. Sure, you can pick different app icon in settings (but you have to upgrade to premium to get a very simple one). But it just ended up prompting me to reconsider whether I need/want the app at all. In the end, it was cathartic to just delete the app.

It’s an object lesson of how important a thoughtful visual design can be (and how detrimental a less-thoughtful one can be, too).

It has been noted before, but I wanted to quantify my impression of a discernible decline in SO activity (through Nov 2024). So, I did a quick SEDE query for SO questions (PostTypeId = 1) per month (and pro-rated Nov). This does not bode well for SO. Not pretty.

This downward trend pre-dates LLMs, but seems to have accelerated since. But a lack of quality answers on platforms like SO will diminish the training data used by LLMs (which are already infuriatingly bad for new or low-volume topics).

Does anyone know of any reason why `AsyncSequence` method `first(where:)` wouldn’t have made the `where` predicate optional, and if not supplied, just return the first element? This `where` predicate is a lovely feature, but it seems like most of the time I want to call `first`, I really just want the first one, and supplying a closure just adds syntactic noise. I end up using an extension to simplify my code, but I’m wondering if I am missing some subtle reason why they chose to require this …
Going through SE-0392 for custom executors, they all involve creating a custom `SerialExecutor`. But there is a simpler approach that I haven't seen discussed much: If you're just trying to get it out of the cooperative thread pool, use a dispatch queue’s `queue.asUnownedSerialExecutor()`.
macOS Sequoia doesn’t seem to remember my granting of “screen access”. Hey, it’s beta, so I get it, but has anyone experienced this and, just as importantly, has anyone found a way for it to remember this setting? I’ll live with it for the beta, but just wondering if anyone has found a workaround…

SE-0316 says, “A struct or class containing a wrapped instance property with a global actor-qualified `wrappedValue` infers actor isolation from that property wrapper”.

Take a second and soak that one in. A non-isolated type becomes actor-isolated because it happens to use a *property* with some property wrapper!

I can guess as to why someone thought that would be convenient, but it is not remotely intuitive.

Interested in getting details about Tech Week in LA coming up in a few weeks. My antivirus software is not happy about that site and I don’t feel like rolling the dice. I wish Bitdefender would tell me a little about how/why they concluded that this site was unsafe…
It would appear that on @MongoDB, that one has to turn *off* the switch next to “opt out of third party cookies” in order to opt out of third party cookies. #backwards