I think WASM's real problem is language fragmentation. For 3D apps, C++ makes sense. But Go and other GC languages don't perform well on WASM - they implemented their own GC anyway. And honestly, I don't see the advantage of writing web apps in Rust over JS. The ecosystem, tooling, and debugging are all better with JS.
A CLI that turns Notion into a Git-like workflow.
Pull. Edit. Submit. Restore.
Every change is revertable, observable, and auditable. Built for AI agents who need to touch your Notion without breaking things.
Quill's a fantastic project and widely used, but it's unfortunately been unmaintained for a while. That's where Quill Next comes in! This is a community-driven fork that we've been actively developing and refining.
We believe it's time for Quill to evolve, and we've put a lot of work into making that happen. Give Quill Next a try and let us know what you think—we're eager for your feedback!
Sounds good. But what are the advantages of implementing a package manager in Rust? I'd think languages with dynamic features would be more
extensible and easier to iterate on.
WASM is to libharfbuzz (when experimental compile time option is enabled) what javascript is to HTML.
So this is essentially native (albeit experimental) libharfbuzz. WASM is used because its how font files are scripted (when using this experimental version of lubharfbuzz)
Its important to keep in mind that wasm is a general technology and is not just used by web browsers.
I've deployed this on my server, and I have to say, it's incredible. I've been looking for an open-source alternative to Airtable for a long time, but none of them met my requirements.
The terminal emulator is a tool that is mostly used by developers. A developer's time is spent mostly interacting with editors and terminals. However, most terminals are not smart enough and have a steep learning curve. Terminal One aims to become a developer tool that is easy to learn, easy to use, and smart enough.