Igneous Linearizer: semi-structured source code

This is an interesting direction.<p>One thought is that obsidian can execute web assembly and a parser &#x2F; sema checker written in something that turns into wasm can therefore be run on the source files. Can probably tie that to a syntax highlighter style thing for in-ide feedback.<p>The other is that markdown is a tempting format for literate programming. I do have some notes in obsidian that are fed to cmark to product html. With some conventions, splitting a literate program into executable code embedded in a html document is probably doable as an XML pipeline.<p>In a much simpler vein, I&#x27;m experimenting with machine configuration from within obsidian. The local DNS server sets itself up using a markdown file so editing an IP or adding a new machine can be done by changing that markdown.<p>I hope the author continues down this path and writes more about the experience.

This is neat, but it does seem like a lot of work to get part of the way to what a Smalltalk already gives you.

this is great! i’ve been thinking about exactly this (though styled after Logseq rather than Obsidian) but not gotten as far as implementing anything.<p>that being said, the thing i haven’t been able to convince myself of yet is why these are different to just normal (in-line) functions? as in, why should i have to write [[foo]]: would it not be better to have all identifiers automatically linked?

I really appreciate the unordinary direction you went with these articles and your site in general. An enjoyable read!

&gt; The solution I&#x27;ve been waiting for is source-code-in-the-database. I&#x27;m cheering on multiple projects attempting this.<p>What are the projects you&#x27;re especially bullish on?