Haha yes I wrote that, thank you for sharing.

We're approaching the problem by drawing from browser design. We want to see an editor with a DOM API for code documents. BABLR is a parser framework meant as a direct answer to Tree-sitter.

▲

WD-42 5 days ago | parent [-]

Myself and most people I know that switch to Zed (many from Sublime) did it because we DON'T want a DOM in our text editor. Webtech makes for crappy text editors.

▲

conartist6 5 days ago | parent [-]

Sorry, I didn't make that very clear. I'm not talking about the HTML DOM, which exists as an API to control the 2D pixel rendering layer.

A standardized DOM for code would provide a universal way of changing code documents using scripts and would allow many different code-oriented tools to interoperate naturally where they never could before.

	▲	dbalatero 5 days ago \| parent [-]
		I think I know what you're saying, and it sounds like an interesting thing to attempt. Some sort of universal API that feels really good to make structural edits to code documents would be excellent.