Google: “[Swift] has matured into a viable systems and cloud language, pairing Rust-like data-race safety with predictable, reference-counted performance.” Announcing their Swift-based cloud SDK for backend services: https://t.co/fGQKYSTKi7
WebSockets are heavily overused for basic data streaming.
If your web app only needs one-way, real-time updates from the server to the client (like a live feed, dashboard metric, or notifications), managing full-duplex WebSocket connections, heartbeats, and reconnect state is massive overhead
Our friends at @duckdb are leaving the nest— Amazon is acquiring the team behind DuckDB. 🦆
DuckDB stays open, the Foundation keeps the IP, and the community keeps growing. A rising tide lifts all Ducks.
What it means for MotherDuck( 👇
I’ve built Swift professionally at Apple as a Staff engineer and since been building Rust and TS.
Here are things @SwiftLang got right that other languages should do 🧵
The gold standard fluid interactions on iOS are built using in-process client animations (like SwiftUI does it) and not render-server animations (like CoreAnimation does it). This is common knowledge inside of Apple’s UI framework and system experience teams.
A close inspection of iOS’s evolution reveals the gradual upgrading of system experiences written using render-server animations (that often disable user interaction) with ones using client animations (that are interruptible and interactive). The app switcher for iPhone X, the Dynamic Island, and Liquid Glass bars are prime examples of this trend.
The other thing that makes these experiences feel so fluid is their use of spring animations that preserve velocity, rather than Bézier curve easing functions. To get velocity preservation, you need to be able to interrupt a spring animation and retarget it or drive it with a gesture. That’s a lot easier to do when the animation is running in the same process as the event handling.
When we were first pitching SwiftUI, two of our go-to demos were a recreation of the iOS 9 navigation and Home Screen interactions which were fully interactive and interruptible, at a time when the actual implementations of those experiences in the OS disabled user interaction and ran server-side animations.
CoreAnimation is great and the framework does much more than animation. You can build a fine app using its server-side animations. But if your UI framework can’t do efficient main thread client animations, there’s a ceiling to the quality of the experience your app can provide.
"Can you use whatever resources you like, and Swift, to generate a short 'youtube poop' video and render it using Swift libraries you have access to (without SPM).
Can you put a personal spin on it? It should express what it's like to be an LLM."
GPT 5.4 xhigh:
me: "can you use whatever resources you like, and python, to generate a short 'youtube poop' video and render it using ffmpeg ? can you put more of a personal spin on it? it should express what it's like to be a LLM"
claude opus 4.6: