Announcing Wanix 0.4-preview and introducing Wanix Elements! Now you can build virtual compute systems with just HTML. Some broad use cases: - run AI in the strongest client-side sandbox - let people try your CLI before downloading - build your own browser OS or dev env - make old apps/games work on the web - explore and play with plan 9 concepts Link below.

Sorry to burst your bubble, but you can't verify your way out of slop. The only way forward is the old way forward: simplicity, clarity, generality. (LLMs are very helpful for that, duh.)

i love good satire but i also struggle with the inherent danger of it

i try hard to remain excited about this kind of insight, so that when people finally discover it we can be excited together. i just do not have the energy to sustain it that long. what even is the winning strategy here

software engineers have been gaslight into believing that software has been solved it feels real, and in many ways is but if you want to build truly ambitious things, it is now even more important to have solid fundamentals and architecture

the fastest inference is no inference. instead of building the final thing, try to build a parametric space that could generate all the possibilities. then move through that space, at zero inference, to locate what you want. code itself is free and instant. don't we dare to forget that.

when everyone else is going slow, accelerate when everyone else is accelerating, slow down

finally set up and tried zerofs and its pretty cool

how long do we have to endure the mainframe era of ai

simplify

There should be a version of usesthis.com/ that's specifically about agents. I'd find that incredibly useful!

"an infinite slop machine, a portable casino, and a 24/7 surveillance device." "an infinite slop machine, a portable casino, and a 24/7 surveillance device." "are you getting it?"

p(doom)=1 on any programmable device, given sufficient time

software incinerator

speaking of hyperreality

My WebAssembly debugger lets you time-travel with your scroll wheel. WebAssembly (and Ghostty) are so fast that a step back just reruns from scratch.

If this Elizabeth Holmes doc is the first time you’re hearing about Nathan Fielder, you are NOT ready to just jump right in. You need to prep. You need to train. You need to build up your secondhand embarrassment tolerance first. Nathan Fielder is advanced-level discomfort.

IMO the essential difficulty of malleable software now boils down to “fork maintenance”. Let’s unpack that a bit. If you want to make your own custom tools or fork existing OSS, the cost of that is headed to zero. But… often we don’t want to start from scratch! We want to remix tools others have created. We want someone else to help us maintain stuff. We want to combine our ideas with others’. Now the moment you have multiple parties both updating the software… you hit gnarly problems! In a nutshell: happens if I modded something and it no longer meshes well with the latest updates from you? This is “fork maintenance”. (Traditionally this would be a centralized model where a “dev” is maintaining the software and you, the “user” might adjust settings or patch things. But even in a more decentralized setting we want to jam with our peers on our tools.) A classic approach here is to expose a stable plugin SDK. Works great because the dev can keep the surface maintained and plugins hopefully compose reasonably…. But only works as long as the plugin surface has what you need. Sometimes you end up hitting walls. If it’s OSS you can also literally fork. Maintaining a fork and merging edits from others is a huge pain. But maybe with enough smart cheap LLMs this is more viable now. You also need to consider data, not just code. Schema migrations are already a pain in the ass with normal software; when every user is doing customizations things get extra gnarly. I don’t think that there’s a perfect solution to this yet. Ideally I’d want something much deeper and broader than a typical plugin API - eg a language or framework designed for layered additive modification (think Harel’s behavioral programming as one reference.) I find it quite poetic that collaboration and working with others is where malleability gets really good but also where it gets hard. Same as many other things in life! For more on this, we go into quite some depth on this topic here: inkandswitch.com/essay/malle…

calling it textual intelligence seems more accurate

A principal engineer showing you their software factory

Introducing erlang_wasm: a WebAssembly runtime implemented in Erlang/OTP. No Wasmtime, Wasmer or wasm3 binding. It interprets WebAssembly on the BEAM. With the compiled tier enabled, hot code is compiled to Core Erlang and loaded as a BEAM module. 64,774 spec assertions passing. github.com/benoitc/erlang_wa…