Oh boy now you found a reason to buy m5 but wait for Mac Studio with at least 128gb unified memory. 😳

What hardware are you building on?

I used claude to structure my thoughts on the subject. Full thread claude.ai/share/1a1c26...

Hummingbird's RequestContext makes this clean: set your per-request environment once, let the framework handle propagation. Vapor does similar with req.storage. No threading parameters through every function call.

The pattern: inject dependencies at request entry, structured concurrency propagates them down the tree. No globals, no TaskLocal complexity. swift-dependencies gives you @Dependency property wrappers that just work.

TaskLocal is for metadata like tracing IDs. But swift-dependencies (pointfree.co/collections/dependencies) extends it for proper dependency injection. Use RequestContext at entry points, structured concurrency handles the rest.

Of course, this means it only works for tree-structured operations—if work escapes the tree, I fall back to safer global patterns (like actors or explicit context passing)

I now use TaskLocal wherever possible for shared state in async workflows, since it keeps context neatly scoped to the structured concurrency tree and avoids many post-suspension surprises.

ServerSide Swift 2025 showed: Vapor, Hummingbird, Swift NIO, type-safe APIs, AWS integration, sub-200ms Lambda cold starts. The ecosystem is ready.

Now build MCP servers, not AI search clones.

serversideswift.info #swiftlang #srrversideswift2025

The opportunity: companies need MCP servers that connect their internal systems—CRM, calendars, accounting, knowledge bases. Not public search. Private context engineering.

Server-side Swift is production-ready for this.

Building MCP servers means handling private data, real-time integration, type-safe protocols. Swift gives you: memory safety, async/await, C++ interop for existing systems, shared code with iOS, Android and Wasm clients.

#swiftlang

MCP isn't "connect AI to more sources." It's AI becoming contextually aware of YOUR ecosystem. Your calendar + email + docs + code. The value is synthesis, not retrieval.

This is where server-side Swift matters. #swiftlang #serversideSwiff2025

Consider swift with c++ interop. Like ladybird browser did. Very interesting post about why here linuxiac.com/ladybird-bro...

Sadly also the Belgium gov has shifted on this subject. www.techradar.com/computing/cy... I wonder what @jbaert.bsky.social thinks of this?

Just double checked temporal, looks interesting. „Pure“ workflows and activities like effect operations, they even have a SideEffect term in their docs. 🙃
Replaying workflows and blocking them indefinitely also looks nice, and it’s language agnostic. 🤔