Fucking Approachable Swift Concurrency
11 points by kevinc
11 points by kevinc
This kinda reads like an LLM wrote it. Is this entirely human work?
I'm convinced it's not entirely human work. Digging a little, it looks like LLMs were used for translation from English. It's at that stage that an agent guidance file was added. Looking at the commits used to create the original English, I think it's initial LLM writing and a lot of editing. If the author had written this by hand, there'd probably be less HTML in the Markdown right off the bat.
This is LLM slop. What is the lobste.rs policy on LLM generated content?
An aspect of the policy is, you're free to flag it.
Here's some context: I followed this page's source material, Massicotte's blog posts since 2024 about Swift 6 era concurrency safety details, as they came out. It's a uniquely good resource because damn near nobody in the Swift community seemed to have figured it out to the same degree. "Approachable concurrency" refers to the round of improvements made after the entire community had trouble with Swift 6 defaults in this domain. So there's been substantial change over the past year and a half. The community has really lost the thread. I shared this article because having it all bite sized and colocated is a new way to have another try at understanding it. Since I can vouch for the source material, I don't really have a problem with the writing style.