Makefile.md – Possibly Use(Ful|Less) Polyglot Synthesis of Makefile and Markdown
zoo.dev
zoo.dev
- JS-based build scripts being replaced with HTML/plaintext polyglot files that serve as both the README and the build script and that run in the universal runtime (the browser) rather than requiring e.g. NodeJS; alternatively
- JS/JS polyglot files that you can run with NodeJS if you so choose but that have first-class support for the browser instead
- JSON/HTML+JS polyglot files that parse as valid JSON but that you save with a .htm(l) extension and provide an advanced browser-based viewer for the data encoded in the JSON (especially typed data, e.g. JSON-LD)
(In general, XML stylesheets leave me conflicted. It’s a nice idea, in principle, but I do not really see a way it could fit into a frontend with more than the slightest amount of interactivity. Also, I’ve lived through the absolute misery that was rebuilding the hefty Nixpkgs manual on every system update using the—quadratic—DocBook stylesheets, and I don’t want to go back to that.)
I’ve had this problem in the past (shudders in Bazel’s WORKSPACE file) and what eventually ended up saving my bacon was org-babel.
Yes, it does mean that emacs is a build-dependency, but honestly literate programming pretty excellent for untangling the complexities of a large build.
cat Makefile.md | npx offmarkThey’d just be plain-ol LMs