In the 80s & 90s, Steve Jobs thought that a computer was a tool to help you make art, and Bill Gates thought a computer was a tool to help you do business, and you can argue whether either or both was right.

But at least neither of them thought that a computer was their personal skinner box to squeeze every last microsecond of your attention in an underpants-gnome-esque scheme to derive share price from… "number go up"

I'd been thinking about "design for engagement" after iBooks unilaterally decided that I would want to set a goal to read for 15 minutes every day. There was no way in-app to disable the behavior, only to change the duration. I did eventually find a toggle to disable it way off the bottom of the screen in the Settings app, but still, how hostile is that? I just wanted to read something, not sign up to define my entire personality by my iBooks usage.

(And whilst I'm being angry, I've remembered to be angry at Finder too — this Finder was bad in Mac OS X 10.0, and it's essentially unchanged in the 24 years since then. They rewrote it from Carbon to Cocoa at some point in that time and took the opportunity to… change nothing. Do they have no ambition? No care? Or does somebody there truly think that this is the unassailable pinnacle of file management?)

Like, who thought this was a good idea? How does one even begin to understand this screen? It simultaneously wastes an incredible amount of space, and is obscenely cluttered. No "hierarchy" is "communicated" by all the overlap, it's just noise. #LiquidAss

@andykorth Why did you star ObjCGameBase in April 2025, at least a decade after its use-by?!

I was literally considering MacGyvering some OSS bits into a replacement IDE just to avoid Xcode. Huge project, but I'm desperate :/

If they're here to break `swift build` too, what would be the point?

Re: https://swift.org/blog/the-next-chapter-in-swift-build-technologies/

Ack, wrong way! Back up, back up!

SwiftPM’s current system is really reliable, and Xcode’s is just *so* buggy. I wanted the announcement that Xcode was abandoning their custom shit to use the open source stuff, not that they were foisting their nonfunctional system on everyone else.

I guess the one upside is that now we can file bugs in the open, but… definitely a consolation prize

So, given Bitbucket are nuking their free tier, and their monthly single-user cost is prohibitive ("$3.30/user/month" — but a minimum of 5 users 🙄), Github are beholden to the devil incarnate (pick which one I mean), and all the other paid providers are even more expensive and/or restrictive (who has only 5 repos?!), am I left with "self-host Forgejo" as the only remaining option?

(meaning that the `onCancel:` block has to anticipate running *before* the continuation has been stored to the lock, and the `withCheckedContinuation` block has to anticipate that it may start "pre-cancelled")

Urgh. TIL (obvious in hindsight, but tomorrow I'll have to audit a bunch of things I've written with the benefit of said hindsight...)

let lock = ...
await withTaskCancellationHandler {
await withCheckedContinuation { continuation in
lock.withLock { // <--- this
// store continuation in lock
}
}
} onCancel: {
lock.withLock { // <--- can race this
// retrieve continuation from lock & forcibly resume it
}
}

#swiftlang

@maia Just wanted to say thanks for sdl3-sys-rs, I'm using it and it's amazing even in early development. I wish more -sys crates took this kind of approach.

(and I wish the community put less emphasis on abstracting away the -sys; I generally find it preferable to work with the C library as directly as possible)

Almost every “Apple person” I follow hated almost every WWDC keynote announcement.

Always hard to judge when or how that kind of shift in public perception will affect a company as big as Apple, but it sure does seem like they fucked up big time.

@helvetica you’ve got a knotty problem with today’s “daily twist”

As someone trapped in the endless grind of mobile app development, ship a new build twice a week, deal with a new OS every year, keep up with the language, keep up with the security, keep up with the design changes, keep up with the fads & fancies, there's something tempting about a return to a world with 1-bit graphics, where a compiler is a thinly-veiled assembler, where apps are 64KB, where swiftc doesn't decide that copying a struct containing a couple strings should bloat your app by 1MB