One of these days I'm going to remember that @swiftlang doesn't finish language features and stop trying to use typed throws.

Today is not that day. I just hit this *again* as I was trying to make a thing that can handle a closure that can maybe throw. And of course, the type of the error doesn't make it through the closure because Swift's release cycle is dictated by Apple's *HARDWARE* schedule.

It's borderline masochism for me at this point. I'm apparently a glutton for punishment.

It's another one of those days where #Xcode is making me want to throw my computer through the window and go become a hermit.

Today it's the fact that if you open a project from an unwritable location, Xcode will pop up this alert EVERY THREE SECONDS UNTIL YOU CLOSE THE PROJECT.

There is absolutely no way to browse code. No way to see how things are being used. No way to stop Xcode from trying to *write data* just for OPENING THE PROJECT. Absolute utter insanity.

All I want for #WWDC is for Xcode to correctly report build status.

Literally nothing else. Fix this and I'll stop complaining about stuff for an entire year. PLEASE.

Other fixes would be nice too, but the #1 thing an IDE needs to do is show correct information. If it can't do that, it doesn't matter what else it can do; it’s not trustworthy.

In a very “Thanos" moment, I decided to brush off some code I was poking at a while ago and see how far I could get myself with simple structured persistence.

Initial results are promising…

Working on writing an article for my site that I've been putting off for years.

Fortunately, the current view is pretty nice, which helps keep the words flowing.