Your iPhone can now run Python, Node.js, FFmpeg... and even Clang 🤯
Introducing the Wasmer SDK for Swift:
→ Run Sandboxes inside any iOS or macOS app
→ 100% on-device. No servers.
→ Near-native speed
No JIT required. Here's how 👇
wasmer.io/posts/wasmer-sdk-s…
Building AI agents? 🤖
Join us at Wasmer’s #SFTechWeek event tonight:
⚡ Live demos
🧠 Conversations with founders & engineers
🥘 Spanish tapas and more
📍 Mindspace, 575 Market St, SF
⏰ 6–8 PM
RSVP if you haven't already →
partiful.com/e/e7nzsUEwK4p3c…
That's an accurate take.
Now is time to define what's going to be the right primitive 😉
AI can write software.
What happens when it can deploy and run it too?
We’ve been building the infrastructure for that future.
Unveiling Oct 5 at #SFTechWeek.
partiful.com/e/e7nzsUEwK4p3c…
It seems the surprise option is on it's way of winning.
If we reach 100 votes the surprise will be a BIG one.
Can't wait to share what's on the oven! 🤗
This is a great example of using the right tech for the problem, and how important is to be always pragmatic with the solution.
In this case, moving from Wasm to JS improved the performance of Three.js' tangent gen by ~4x and the size by 75%.
Keep up the good work @mrdoob!
More WASM code replaced with simpler and faster JavaScript 🥲
github.com/mrdoob/three.js/p…
Small update: we just got Postgres fully running on iOS as well!
xitter.cf/wasmerio/status/210323…
Yesterday we announced Python, Node.js and FFmpeg running on your iPhone.
Today: a real PostgreSQL 18.4 server. On iOS. And in your browser. 🐘
No backend. No cloud. Just WebAssembly.
Try it right now 👇
wasmer.sh/?example=postgres
🚀 We very have very exciting updates!
Safari and Firefox can now fully run Node.js, Python and more using the Wasmer JS SDK.
Try it online and let us know your thoughts. Can't wait to see what you build with it! ❤️
wasmer.sh
This environment exists today: is called Wasmer.
Wasmer can run bash, Node.js fully (including Next.js, Astro), Python fully (including FastAPI, FastMCP and Flask) and even PHP 🤯
In the browser, embedded, or in the server
MCP vs CLI for LLMs is the wrong discussion. People are debating at the wrong layer.
Both work incredibly well as long as they are run through a repl like environment that can persist state. The funny thing about CLI is that CLI tools are usually accessed through BASH which happens to be a repl with persistent state (the file system), therefore cli works much better than mcp. But this isn't even close to being an intrinsic property of MCP. Just means that we need better harnesses.
Right now the best repl for this are:
- bash + fs
- jupyter kernels
- codemode type repls, usually quickjs
LLMs understand the concept of forward evolving a system to solve a need very well. This comes from the agentic RL. They understand how to change the state of a codebase or acquire data from databases and then operate on it similarly to humans. But without an execution environment, they actually cannot do this properly.
My bet? Sometime soon someone will (or has already?) create a embeddable, sqlite style mini execution environment that parses bash, typescript, or tool calls into a common IL execution plan that's easy to security check before executing. And design this specifically for durable execution environments. Then we will just connect cli, mcp, webmcp, whatever to that and it accepts any of the input modalities as they can all be represented as each other.










