5 ms·

This is a quite an interesting architecture that could also be used for developing on the browser. I imagine some of the existing browser development tools use

• cxr 6y ago
  I've been advocating for this type of thing, especially since a lot of the tooling around NodeJS is so bad, viz: https://news.ycombinator.com/item?id=24495646 https://news.ycombinator.com/item?id=24495646 For my personal site, I switched to Marijn Haverbeke's Heckle <https://marijnhaverbeke.nl/blog/heckle.html https://marijnhaverbeke.nl/blog/heckle.html> several years ago. I realized that I could pretty easily do a rewrite that uses my browser's native JS engine + browser APIs instead of requiring NodeJS and depending on the slipshod fragility of the NPM ecosystem. The result is triickl: https://codeberg.org/triplescripts/triickl https://codeberg.org/triplescripts/triickl What's more is that, because I also created some tools that allow triickl (and similar programs) to be packed into a single, self-contained file that can run in the browser (e.g. buildfoo.html or pages.app.htm), it's pretty natural to let there be a page on the target site corresponding to this file. The end result is that if you're using triickl, you can clone the site's source repo and then use buildfoo.html to generate the static assets. In other words, so long as you're able to get your hands on the source tree, then every computer is already a development system.