3/3 The public layer is moving to tangled.org. AT Protocol-based, no surveillance business model baked in. If you're thinking about the same move, I can share the setup.
Posts by Stijn Willems
2/3 I'd been playing with jj (Jujutsu) as a git replacement anyway — not to flee GitHub, just because it's better. The data grab made the decision easy. All my code now lives on a European Hetzner server. Fast. Boring. Mine.
1/3 GitHub flipped Copilot training data collection from opt-in to opt-out. That's not a privacy policy. That's a reversal disguised as a setting.
Will start using it tomorrow had to do a little prepping first
Jujutsu, a new favourite of mine, offers more manageable workspaces than worktrees. Check it out on GitHub: github.com/jj-vcs/jj. I’m also considering moving from GitHub to tangled.org which works with atProto. Give it a try!
Swiftly use Xcode should solve that if you run it
The 'no Xcode needed' part is the real unlock. Xcode has always been the steepest entry tax for Swift. Vibe coding removes the toolchain friction and lets the logic come first. The IDE becomes optional.
Wendy allows you to write Swift for a variety of embedded devices.
Jetson & Raspberry Pi - and even microcontrollers!
Swift 6.3 has landed! 🚀
This release brings community-driven Android support into the official toolchain, along with major improvements to C interoperability, the build system, and embedded Swift. Read more: www.swift.org/blog/swift-6... #AndroidDev #iOSDev
Building a coding agent in Swift from scratch https://github.com/ivan-magda/swift-claude-code (https://news.ycombinator.com/item?id=47515605
Very dangerous putting a wrapper around another concept that does the same thing with async streams. But if it helps you. I was long convex I’d it would too but after Rxswift and its variants bit me way to many times it is just not worth it. It simply does not scale.
Look genuinely interesting and something I will give a spin. Nice!
I recently released sequins.dev, to have all the Observability signals you expect like logs, metrics, traces, and profiles, but as a macOS app which you can use for local dev. It's also completely free and open source.
Give it a try, and let me know if there's any features you want!
Soft-launching a lil' side project I've been working on!
Say hello to Tablinum - a local-first database with built-in sync, collaboration and data persistence!
tablinum.dev
github.com/rryam/Vectur... check this out and use these skills github.com/wendylabsinc... will help. Also ask Claude or another agent to build you a skill for learning swift from a python perspective.
Screenshot of Ghostmoon.app - a utility app for macOS.
Ghostmoon.app [pre-release]
I created a macOS utility app called Ghostmoon. It lives in the macOS menu bar and gives you easy access to hidden system settings, essential stats, maintenance routines and other functionalities useful in everyday work.
#macOS #menubar #prerelease #IndieApp #Mac #Swift
Sorry managed to scramble my replies wit for SwiftUI you can use this. ViewModifier or dynamicProperty
Gotcha: SwiftUI only resolves it when stored directly on a View. Nested or dynamically created → silently nil.
so most cases, I preferred the ViewModifier approach
Yes defiantly especially as SwiftUI is ‘t a is you avoid mvvwm and use environment as suggested you do not need all of that with similar or more build in composability
For dynamicproprerty to work it needs to be initialises in the view hierachy. Unfortunately that also excludes init. Only properties work.
Yes, used it. Hidden singleton under the hood — the "container" is global state with a nice API on top.
Yes swift is annoying at this level. Glad to hear someone other stating that the envisioned value outways the pain. On darker days I sometimes forget. Thanks for the reminder.
Xcode local archive panel for the macOS app target “Preflight-macOS-AppStore-Release.” The left shows the app title, the right column lists many builds in chronological order: each line reads “Build Today, [time],” with a yellow warning badge on the latest entry and red hazard icons for all previous builds, indicating failures for a whole day until it succeeds
The joy of C++ interoperability with Swift.
The pattern is the same across everything we build.
A tool that “seems good” is an intent claim.
A tool that survived debate and proved itself against the roadmap is a structural claim.
AI suggests. You decide. Then you hold the line.
Next milestone: ditch GitHub entirely.
It doesn’t work with 100 PRs a day. Agent swarms expose every bottleneck built for human pace. GitHub is human pace.
Last incorporation after days of debate: abandon git + Graphite for jujutsu.
Paid off. Without the gate I would have drifted to Radical — looked good, but didn’t hold me to the roadmap.
The debate surfaces that. My impulses don’t.
Every tool I see has to pass a debate before I touch it.
Not a quick scan. Agents trained on my roadmap, arguing for and against. I sit in judgment.
This is not caution. It is governance.
Hot take: half of LLM use for code editing is safe refactorings that intellij was able to do ages ago, but primarily just in Java, and never quite reached this level in other languages... For better or worse, we now can, but with lots of $$$ burnt each time you do huh
To counter balance my previous agents tweet about source code editing. In having a load of success outsourcing simple tasks and fix up's to agents and aid in research of codebases or problems. Also "try these 20things to reproduce, minimize a reproducer" and stuff like that.
This made me genuinely happy.
An AI agent gets dramatically more accurate when you tell it: debate what you're unsure about, and stumbling is ok.
We build tech like we raise children. Tech meetings should start talking about love in their stack.