… then use the next couple of years wisely.

Go after the criminals, and prove the crimes. Develop *fair* plans to fix the systemic weaknesses that are now very apparent.

Do it the right way, and don’t just vindictively put the boot in. Don’t fall into the “beat them at their own game” trap (c.f. morally bankrupt and idiotically counter-productive Dan Sullivan spoilers…)

All that being said, celebrate the victory, and fuck the fascists.

I want to think the political tide has turned in the US, but a word of caution from the UK.

We elected a progressive(ish) government 2 years ago. Many voters were motivated to switch by economic self-interest and a desire for change - not a political Damascene conversion. They complained when everything wasn’t magically fixed in the first ten minutes, and may switch back.

T’was ever thus: but worth keeping in mind. You have two years to make it about more than the cost of diesel and groceries…

Waking in up in the UK to some positive news from the other side of the pond is a welcome change…

Mind you, it’s the hope that kills you.

RE: https://tenforward.social/@nivex/117486661160031283

This, in a nutshell, is how I feel about AI too.

Sean has put his finger on what I find so distasteful about a lot of the AI discourse at the moment.

Too much of this, and too many ad hominem attacks in general. Play the ball folks…
https://www.seangoedecke.com/dont-diagnose-your-opponents/

More food for thought.
https://seangoedecke.com/softwares-centaur-age-may-last-decades/

Cartoon from the latest Private Eye, with a different perspective on the whole thing…

I’ve been in roles where pretty much all I did most days was review other people’s code.

It wasn’t always what I wanted to be doing, but we were trying to establish a review culture and a coherent architecture - and not just a bunch of loose cannons working away in their own corners - so I took one for the team*.

Maybe that’s one of the reasons I’m not so freaked out now by the idea of not writing most of the code myself?

(*whether this was the right approach is a whole other question)

Anyone have any colour printer recommendations for my mum, who is an artist and does a lot of photographic printing?

She has a reasonably modern MacBook Air, but not a lot of space.

I keep pushing her towards a laser as she’s had a succession of bad ink jets, but they tend to be too bulky.

Sadly my dad took ill just before WWDC, and died a few days later*, so I'm a bit out of the loop.

I'm finally back home, and would welcome thinking about work for a bit.

I don't get the impression that I missed much at dub dub. Is there anything particularly worth catching up on?

(* dad had dementia, and was not in a great state physically or cognitively, and so his death was a paradoxical mix, both expected and unexpected, very sad and something of a release for him)

This warning is one of those pebble-in-the-shoe things that really irritates me.

It's caused by enabling the Thread Sanitizer, and it's been in XCode for a long time.

"It's harmless”, I hear you say, “just ignore it.”

Well no.

It may be harmless, but ignoring warnings is not harmless.

Having one you can't get rid of normalises that ⚠️ icon showing constantly in the toolbar, issue navigator, and editor.

Which means you stop looking, and don't notice other warnings.

Which is shit.

It's easy to be sentimental about Apple. They were always ruthlessly commercial, their execution was just patchier before Cook.

It used to feel that profit was the means to an end though. The end was making great products.

Now it feels like the profit is the end. There has been a slow erosion of the culture that made them different. Or perhaps it was an illusion all along.

I think the Apple board have to share responsibility with Cook for the culture.

Pandering to Trump is merely a symptom.

Later on a build a command-line replacement (https://github.com/elegantchaos/novy) for it.

Now I'm tempted to make a SwiftUI shell that wraps the command line version and just works via a global shortcut and/or a menu extra.

I was hoping that all these years later there might be an official extension point for adding context menus to the Finder.

Sadly it looks like I was hoping in vain 😢

A couple of people got in touch with me recently about an ancient app I used to make called Neu (https://elegantchaos.com/neu/). It was written in Obj-C and I basically stopped working on it about 13 years ago, because Apple's sandboxing restrictions were making it hard to do what it originally did (which included adding a context menu to the Finder).

Amazingly these people are still using it, and it works on macOS 26.0. This makes perfect sense, but I'm still somehow surprised.

I know a lot of people have moved away from Github, but I've been working on an update of ActionStatus, my CCMenu-style helper for monitoring Github Action workflows.

There's a testflight up if you want to test/break it: https://testflight.apple.com/join/2EVFt38W

(FWIW the website is here, but doesn't have a lot more info on it at this point https://actionstatus.elegantchaos.com/)

I'm thinking I might add support for some other services (codeberg? something else?) depending on what people use and whether anyone cares 🙃

To be clear:

the local private `resourceBundle` is not marked as `nonisolated`, so inherits the target's default main actor isolation.

Even if this weren’t the case, the generated `Bundle.module` is also not marked as `nonisolated` and so that also inherits the target's main actor isolation.

This is true even with `.enableExperimentalFeature("SendableProhibitsMainActorInference”)` turned on for the target (Bundle is Sendable according to the Obj-C header file).

This seems to be the ultimate root of the problem:

https://github.com/swiftlang/swift-package-manager/issues/9656

which results in:

GeneratedStringSymbols_Localizable.swift:11:25 Main actor-isolated default value in a nonisolated context

which makes perfect sense.

Does nobody test this stuff?

whereas 26.4 does this:

private let resourceBundle = Foundation.Bundle.module
@available(macOS 13, iOS 16, tvOS 16, watchOS 9, *)
private nonisolated let resourceBundleDescription = LocalizedStringResource.BundleDescription.atURL(resourceBundle.bundleURL)