i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird
- I have maybe 20 websites (mostly static but not all)
- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most
- I need to be able to ignore a project for 3 years and then come back and be able to develop it easily
i feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
a few people have been asking what my typical setup is for "running websites that I can completely ignore and spend 0 time maintaining" so I wrote down a few thoughts
https://gist.github.com/jvns/5bd9283d7abd5ceb26eb7ed28afe3030
> Don't use a Javascript build system
@b0rk I worked around this one for my go single binary servers, by using esbuild (which is a go application) with a go generate that wraps it as a library at build time.
However this is just for simple bundling, it doesn't support fancier stuff like typescript compilation.
Actually as I write this I realize that it would probably not meet your requirements, as this setup also needs a yarn/npm install to download the dependencies from the internet if there are any.
@mariusor yeah I do use esbuild, I think 2 of my projects use esbuild and I like it. I usually prefer to avoid it though.
@mauve I use esbuild as a library from tooling written in Go and so far (about 3-4 years) the API was pretty stable.
@b0rk