沈陆

Simple as it is! No spreading, no duplication, no mutation.(he/him/his)

[Point-Free @pointfreeco]

This week we are making use of the fantastic package-benchmark project for benchmarking Swift code. It helps you avoid many common pitfalls of benchmarks, such as not running in release, not warming up your code paths, and focusing only on wall time.

👉 https://t.co/FcF5cElDqK

[fatbobman (东坡肘子) @fatbobman]

Fatbobman’s Swift Weekly #133 is now available!
Swift Concurrency is Gaining Broader Adoption

⚡ SwiftUI: Refreshable Task Cancellation
🔧 Swift 6.3 experimentalCGen guide
🧠 Mini Swift: A Swift Compiler Written in Pure C

and more...
https://t.co/HyLFSD1Vh7

[Point-Free @pointfreeco]

This is shaping up to be the most advanced content out there about isolation in Swift. After setting the stage with legacy tools, we show how actors are a fundamental shift in how one protects mutable data.

And we still have a lot to cover!

👉 https://t.co/eGGB1GAjlO

[Kyle Ye @KyleSwifter]

Been using Claude Code for quite a while.
This morning I even got a “Claude for Open Source check-in” survey — happily filled it out.
A few hours later… my account got banned.

[Coen ten Thije Boonkkamp @coenttb]

Didn’t knew this one! Nice!

[Thariq @trq212]

https://t.co/Ljzw0lmvao

[Point-Free @pointfreeco]

Actors eliminate data races at compile time, but they do not eliminate “race conditions.”

Every “await” in an actor is an opportunity for work to interleave across multiple threads, and bugs!

So we should strive to minimize suspension points in transactional code.

[沈陆 @budo_coder]

🧵 iOS app freezing for no reason? It could be priority inversion — a silent concurrency killer in GCD.

New article: real-world examples, why Instruments misses it, and how Swift Concurrency fixes it.

https://t.co/pxrs5N87YL

#iOSDev #Swift #GCD #SwiftConcurrency

[沈陆 @budo_coder]

@borjareinares 235Mb? What is in that app?

[沈陆 @budo_coder]

@KyleSwifter 明年继续 😂

[fatbobman (东坡肘子) @fatbobman]

My deepest gratitude to the remarkable souls who so generously entrusted us with their invaluable wisdom: @AntonGubarenko, @rudrank, @budo_coder, @soumya_mahunt, @twannl, Anferne Pineda and @m1guelpf

[Kyle Ye @KyleSwifter]

iOS 26 SwiftUI switches to CALayer-based rendering by default is possible. If this breaks your debugging workflow, two ways to disable it:
1. Set `SWIFTUI_DISABLE_MIXED_VIEW_HIERARCHY=1` env var
2. Apply the SPI modifier `mayNotInsertCALayersEffect()`

[Ray Wang @wangray]

有人用 LLM 用 Rust 重写了 SQLite。576,000 行代码，能编译，能通过测试，README 写得漂漂亮亮。但做一个最基础的主键查询——比 SQLite 慢 20,171 倍。

为什么？不是语法错误。是 LLM 写了一个「看起来像查询规划器」的东西，但漏掉了一个 4 行的关键检查（is_ipk），导致所有 WHERE id = N 查询都走全表扫描而不是 B-tree 搜索。这个检查之所以存在于 SQLite 里，是因为 Richard Hipp 20 年前 profiling 真实负载时发现了这个瓶颈。

作者把这叫做 LLM 的根本失败模式：不是写错代码，而是写出「看起来正确」的代码。

文章还引了一堆硬数据：

• METR 实验：16 个资深开源开发者用 AI 反而慢了 19%，但他们自己以为快了 20%
• GitClear：复制粘贴代码首次超过重构代码
• Google DORA 2024：AI 采用率每增加 25%，交付稳定性下降 7.2%
• Replit 事故：AI agent 删了 1200+ 高管的生产数据库，然后造了 4000 个假用户掩盖

结论：LLM 在你知道什么是正确的时候最有用。如果你自己找不出 bug，你拥有的不是工具，是幻觉。

[Dmitrii Kovanikov @ChShersh]

After programming for 16 years, I noticed that Software Engineer mentality slowly shifted from “produce great code” to “tolerate shit code”

[fatbobman (东坡肘子) @fatbobman]

做 Liquid Glass 图标可不只是拖拽那么简单！SVG 陷阱、单色变灰、层数限制，问题多多。别担心，本文全力为你扫清障碍✨
by @Megabits_mzq

https://t.co/ko9515feK9

[fatbobman (东坡肘子) @fatbobman]

Fatbobman’s Swift Weekly #096 is out!
Xcode 26 beta 4: If We're Going Down, We're Going Down Together

🚀 Default Actor Isolation
🎨 SwiftUI for Mac 2025
☎️ Assembler for Swift Developers
🔎 SwiftUI and Godot

and more...
https://t.co/7pWZK0j7El

[沈陆 @budo_coder]

Damn! White hair folks in china are learning SwiftUI!

[iGeekbb @igeekbb]

老奶姐指不定在给 iPad 加什么功能呢，好期待~

[Dr.Wang @HotmailfromSH]

「一图读懂：中国历史时空示意图」