Working on Wasm @figma. Previously @dylibso @datadoghq and @recurly.

New Orleans, LA
Joined May 2011
ah yes a figma file with a code layer loading our figma prototyping playground with a code layer loading our figma prototyping playground
2
13
420
Benjamin Eckel retweeted
Now teams can explore and build code-backed prototypes on the canvas with Code Layers, now in open beta 0:00 Intro 0:43 Starting from code 2:26 Explore code concepts on the canvas 3:57 Edit in both code and design 6:36 Merge ideas together
25
33
8
484
1,226,061
The first time I worked on a public product, a very influential dev on this platform said some flippant and bad things about it. I have almost no influence or reach, but I still try to think about that before I post. Most products are made by people who really care for them.
1
1
10
574
Benjamin Eckel retweeted
work in progress in erlang wasm github.com/benoitc/erlang_wa…
2
5
2
62
4,331
Benjamin Eckel retweeted
I'm making a recent project public: Weave: Universal Live-Migration and Snapshot/Restore for WebAssembly, across many of the most supported runtimes and hosts, including Web, Server-Side, and Bare-Metal. github.com/dphilla/weave Toyed with this idea like 5+ years ago, made small attempts with free time here and there since then, but Sol + Astra helped push it over the line in the last couple of weeks to this beta. Yes, I used AI assistance, as we basically all do now. Yes, the code is more verbose than I would like. No, this was not "vibe-coded". All that is to say though, I finished it in about 1/50th of the time it would have taken me otherwise to get it to a beta release like this, especially because of the extensive experimental period it took to decide on technical direction and architecture, which imo is where the current models really shine, even more so than straight code gen Check it out, feedback extremely welcome. Also, definitely seeking contributors to push it forward if anyone is interested, as I won't really have time to work on it in the foreseeable and immediate future. Note, this is a different type of thing than if you wanted to, say, live-migrate a Linux VM, or other virtualization abstractions tied to or emulating bare metal archs or those tied underlying kernels and storage and networking facilities or similar; some similarities, but several glaring differences. It's still a WIP, please hmu if you want to get involved and help out on it. DEMO: Weave. Technical details below --
4
6
1
43
4,320
Benjamin Eckel retweeted
I’ve alway’s thought it’s a shame that WebAssembly has the word “web” in it. Gives it a connotation that it’s “only for browsers” or something. Meanwhile, NASA’s over here with a flight-compliant derivative (SpaceWASM) intended for spacecraft! The intent is writing mission software to a standardized bytecode, where the end platform / ISA is otherwise arbitrary. In other words, run the same mission package on ARM, Rad-hard PowerPC, RISC-V, whatever. Thus, after-flight you could (safely) upload new payloads with “approved” APIs. Weird to think about, but just like buggy WASM code shouldn’t crash your browser…the same logic applies to not crashing your critical flight hardware.
93
338
42
4,931
293,551
Benjamin Eckel retweeted
Introducing Dactyl Dactyl is a vibe coding platform for native iOS and native Android apps. What's interesting about it is the device simulator: we've built a SwiftUI renderer in WASM. This means as you're developing, you get low latency in browser canvas simulation of the app to play with. Also things like oauth flows happen in the browser. If the app uses the camera - the browser camera API allows us to display it in the simulator. We also let you connect your ChatGPT subscription so you don't have to buy tokens through us (+ markup) Through [magic] - we can run the same SwiftUI code the agent writes for iOS in android, with native components. This is the work of @undefined_void (primarily), @piscisaureus, myself, and others at Deno. It's built on Durable Objects perhaps unsurprisingly dactyl.dev/
91
177
66
1,824
265,802
Benjamin Eckel retweeted
Plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins on plugins
23
13
202
40,662
Benjamin Eckel retweeted
This is crazy. You can recreate Photoshop filters directly in Figma by simply asking 🤯
10
14
3
276
15,481
Benjamin Eckel retweeted
So cats is out of the bag...😺 This is what I've been working on for the last 2 months @figma. You can now create plugins in Figma at the speed of thought, no coding needed! I'm so incredibly proud of the work the team did on this. Do me a favor, generate some plugins! Credits are free during open beta!!! Give us ALL the feedback. We can't wait to see what you build!
Generative plugins, built by you and the Figma agent Describe the tool you need: behaviors, controls, parameters and get exactly what you want for your workflow Live from Config 2026
18
7
130
12,909
Earlier this year I worked on giving agents access to our custom embedded JS runtime to script the canvas. Now it's one of the core primitives behind our new first party agent :)
wdym of course there’s an agent right on the design canvas that’s fluent in Figma and native to the way your team works
1
1
16
1,892
Benjamin Eckel retweeted
This works in a clever way—by doing code generation against Figma’s Plugin API, so Claude is translating your app code into Figma functions. From my experience it makes it much more reliable!
12
2
2
178
38,853
Benjamin Eckel retweeted
Today’s Figma MCP update makes it one of the strongest integrations with Claude Code I’ve seen. You can now use Claude Code to design in Figma with the the full context of your design systems.
Now you can use AI agents to design directly on the Figma canvas, with our new use_figma MCP tool and skills to teach them. Open beta starts today.
253
369
55
6,212
1,136,362
I'm a big believer in the idea that code is the ultimate "handle" for an agent to manipulate your app. Really excited to work on this with the team.
Now you can use AI agents to design directly on the Figma canvas, with our new use_figma MCP tool and skills to teach them. Open beta starts today.
3
123
Benjamin Eckel retweeted
can't believe @wasm_io is less than a week away! @and_prf and I will be there for our session "The State of Zero-Dependency Wasm" with the latest from #wazero and #chicory 🚀
1
3
1
4
415
Benjamin Eckel retweeted
Major breakthrough tonight! After several weeks getting the C-based Prism Ruby parser hooked up to the Chicory WASM runtime (AOT compiled to JVM bytecode), I now have a local version of the gem that uses *zero* native libraries. Write once run anywhere indeed!
3
10
66
3,789
With AI being so close to passing the Turing test, we were all afraid of AIs impersonating humans. But because of the financial incentives around AI investment, we're ironically seeing humans impersonate bots.
1
1
194
Quick life update, I'm no longer the CTO of Dylibso. I'm now working as an IC at @figma. Really excited to continue my work at a place that values the things I love: Wasm, extensibility, and building for creators. simst.im/articles/why-i-join…
1
5
149
Benjamin Eckel retweeted
Much love to the @CloudNativeFdn Helm team using Extism to power v4's new plugin system. helm.sh/docs/overview 🎉 Congrats on the new release!
2
4
8
1,096
Benjamin Eckel retweeted
I'm looking to hire someone to help me build KCL! It's a programming lang for 3D design that we're making at Zoo. You'd be working closely with me on the KCL interpreter, the CAD API it calls, and our mechanical engineers. Rust-heavy role. zoo.dev/jobs/4619187005?gh_s…
8
2
9
976