Pinned Tweet
Swift 6.2 concurrency journey:
- Start single-threaded.
- Introduce asynchrony for latency.
- Embrace concurrency for performance
- Leverage actors for robust state isolation.
Ramit Sharma retweeted
For a sw engineer, there is practically no upside but large downside side to be an asshole to a fellow engineer on this site.
It is a career limiting move: because no one wants to hire a jerk (or have a jerk as a new colleague)
Unless you’re checking out of tech: why do it?
SwiftUI's segmented picker looks cleaner on iOS 26.
The selected segment is rounder, and the thin separators between segments are gone. The code stays the same.
Ramit Sharma retweeted
🥇 SwiftUI Performance: Find Redraws in Xcode Instruments
avanderlee.com/swiftui/swift…
🥈 How to reduce token usage in Claude Code, Codex, and Cursor
avanderlee.com/ai-developmen…
🥉 Sendable and @Sendable closures explained with code examples
avanderlee.com/swift/sendabl…
#swiftlang #swiftlee
Overlay style ArrangementView stacks the two views most of the time.
In a fold they sit side by side, with First View on the right — not the same as split.
Ramit Sharma retweeted
🏁 SwiftUI vs. UIKit 🏁
Build a native version of the chat screen in Campfire. One prompt, but this time with skills. SwiftUI got Apple's Xcode 27 skills, UIKit got ones I wrote.
Winner is UIKit 🥳 (2-0) vs. SwiftUI.
UIKit/Swift passed every test.
UIKit/Objective-C was the fastest and used half the memory 🏎️
SwiftUI is still slow (5s of stutters!), even with Xcode's swift-ui-specialist skill.
What would you like me to test for round 3? Code is in the repo (next comment).
Ramit Sharma retweeted
Replying to @hishnash
@hishnash and @natpanferova tried turning their books and articles into agent skills, but coding agents didn't pay enough attention to static skills.
So they built SwiftFairy: a local macOS static code analyser with an MCP server for your coding agents!
go.peterfriese.dev/ai-swiftf…
Ramit Sharma retweeted
ArrangementView in SwiftUI: split and overlay layouts for iPhone Duo nilcoalescing.com/blog/Arran…
Ramit Sharma retweeted
ArrangementView is a new SwiftUI API in iOS 27.1 that takes some time to get your head around, so I wrote a post exploring it on iPhone Duo, with lots of examples of how split and overlay layouts adapt as the device folds:
nilcoalescing.com/blog/Arran…
Ramit Sharma retweeted
Premature agentization is the root of all evil.
—Me, with a nod to Donald Knuth
Claude Code desktop app is actually the best imo
Ramit Sharma retweeted
I really wanted to see what the HomeView setup UI looks like on device, so I adapted my little ESP32 Apple accessory emulator firmware to broadcast its Bluetooth advertisements 😅
Ramit Sharma retweeted
What if you could build websites the same way you build SwiftUI apps, declaratively in pure Swift with no HTML required? That's the idea behind Ignite, and it works surprisingly well. 🔥 hackingwithswift.com/article…
In iOS 26, toolbar items next to each other share one glass capsule.
To split them, put a ToolbarSpacer between them.
RT @GergelyOrosz: GitHub has more AI-generated PRs than human-written ones already.
There are ~3x as many AI-generated PRs than human-writ…
Ramit Sharma retweeted
Peter Steinberger, the creator of OpenClaw, open-sourced the exact setup that keeps Claude Code and Codex on the same rules
One AGENTS.MD, 69 skills and a sync script that links them into both agents on every machine he uses. 6.6k stars, MIT.
What is inside:
> 7 rule sections, from tone to git safety
> 69 skills, each with a description the agent reads before loading it
> 4 helper scripts with zero dependencies
> 1 pre-commit hook that checks every SKILL.md
> 5 slash commands: /handoff /pickup /fixissue /landpr /raise
> 1 tools.md listing every CLI on his machines
They hand work to each other. codex-first has Claude plan and review while Codex writes the code, autoreview loops on the diff, and handoff packages state for the next agent.
Fork it, run scripts/sync-skills, and replace his hosts and accounts in AGENTS.MD with yours.
Ramit Sharma retweeted
How to deal with complex features that might need 40–50 async requests to populate the screen? How might we arrange these requests to prevent overwhelming the Cooperative Thread Pool, or how could we refine concurrent tasks?
swiftwithmajid.com/2026/09/2…
























