3 ms·
>Yes! That the markdown sources should be the only source code for a series, and that Rust files, terminal sessions, even screenshots should be "build artifacts
by dhosek 5y ago
>Yes! That the markdown sources should be the only source code for a series, and that Rust files, terminal sessions, even screenshots should be "build artifacts", that can all be produced from the markdown by my content pipeline.
Sounds like somebody's re-inventing literate programming.
- fasterthanlime 5y agoDriving right past the snark to point you at https://github.com/dvcrn/markright https://github.com/dvcrn/markright, whose author recently contacted me, and is going for something really similar to what I've tried to describe in my article. Markright (& my own thing) are focused on iteration: you can think of the output as a Git repo, rather than just the end result. I've also never seen a literate programming system that generates colored terminal output, screenshots, etc. I'm not sure why you chose to write this comment that way instead of saying "Seems like a neat derivative/evolution of literate programming", which wouldn't imply anything negative about anyone, but here we are!
- newplagiarist 5y agoI can't touch on outputting a git repo, but org-babel can definitely give you colored terminal output and screenshots, etc. But I love to see people play in the literate programming space and loved your article.