Post

And another Quarto announcement; I've alluded to it before, but we're making it "official". We've started work on Quarto 2. The blog post has an overview: quarto.org/docs/blog/po... We'll share more in future blog posts, but here's what you can expect from the Quarto 2 dev effort: (1/)

Quarto 2 is rewritten from the ground up in Rust. The performance-critical parts of the system are now entirely in a single source tree, which will give you much faster Markdown processing, as well with more thorough tooling support like error messages, lints, and completion. (2/)

Because the main code base is now fully in Rust, we can compile it to WebAssembly, and use it to drive a web-based collaborative writing system. This is based on www.automerge.org, and will have both open-source and commercial hosted versions. (3/)

We also figured out how to make the processing pipeline "bidirectional", allowing rich editors to conveniently and minimally change the .qmd source in editor environments. This will bring a number of new affordances that aren't demoable yet, but we think you'll truly love. (4/)

Nice! I hooe the apis for this will be exposed, I myself and I am sure many others will want to build quarto and native .qmd support into many things (obsidian, web, anything electron, maybe even into agentic coding gui’s?)

The happy path to the infra will go through buying in to our syntax and processing pipeline, so I don't think obsidian folks will want to do it. Or, at least, it won't be a trivial, one-afternoon affair. But we're definitely eyeing a rebuild of our own visual editor on the technology. Stay tuned.

I was thinking an obsidian plugin as a container for this… my thinking is there is a spectrum form technical to prose, each with editor preferences, could see a variety of solutions all of which run on .qmd as a commonality..