Tangentially related, I did a project (forked, but fully rewrote) to be able to avoid the Package.swift file for single file projects like these. [1]
The general idea is a bit like uv if I have understood uv correctly. Basically you do your imports normally and add a comment next to them that tells where the imports should be found. Then instead of running your project through swift directly you run it through swift-sh (or `swift sh`, swift will find the `swift-sh` binary automatically, just like git does for plugins). swift-sh will download and compile the dependencies, then add the proper options to swift so it will know where to find them.
It is even possible to add a regular shebang to swift-sh at the beginning of the file, chmod +x it, and just run it like a regular script!
Or use swift-sh to compile it.
(And installing swift-sh itself is as easy as `brew install xcode-actions/tap/swift-sh`.)
Did you use it recently? I used it to translate a Chinese website to English and was surprised to see everything made sense. Even the texts on the images were translated (in Safari).
Agreed, but do you honestly think LLMs have reached the level of average programmer? Or is it more a matter of "they can churn out code until I see something that is close enough and I'll make the last few edits"?
Also curious if you publish your working setup or if it changes as fast as the LLMs? Seems like you may have a more stable setup than most given how you are developing tools in the space.
I still do not see LLMs as replacements for programmers - they're tools for programmers to direct. If you don't know anything about programming you might be able to get a vibe coded prototype or simple tool out of them but that's a very different thing from a what happens when a skilled software developer uses these things to help accelerate their work.
My current setup is mainly Claude Code CLI on macOS and Claude Code for web driven by the iPhone all and macOS desktop app. I occasionally use Codex CLI too.
I expect I'll be on a different default combo of tools within a month or two.
> The Daily WTF at least once. That's representative of the average
I'd say The Daily WTF are the more spectacularly weird and wrong, not representative; I've seen a few things deserving to be on their site in real life*, but the average I've seen has been much better than that.
It's difficult to be sure, but I think these models are roughly like someone with 1-3 years of experience, though the worst codebase(s) I've seen have been from person(s) who somehow lasted a decade or two in the industry.
* 1000 lines inside an always-true if-block, a pantheon of god classes that poorly re-invent the concept of named properties, copy-pasting class files rather than subclassing even after I'd added comments about needing to de-duplicate things in them, and that was all the same project.
No, no one has ever known anything, and every day people are born knowing even less. This is a strangely aggressive way to share this interesting information, especially for MacOS programming, a platform requiring such byzantine arcane knowledge I'm amazed people write anything for it at all. At least for Win32 people wrote books you could buy and not blog posts.
Anyway, thank you for the introduction to the very cool SwiftScripting project [0], extracting programmable interfaces directly from app bundles. It's just like COM, right? nice to see MacOS catching up (/ragebait)
Also, FYI the interesting part about the post is getting the extracted code in type-safe Swift code. Getting the extracted code for ObjC is trivial and any seasoned macOS developer should already know how to do it.
reply