Go + PostgreSQL. I'm still finding that making the actual HTML part in Go is a bit frustrating. Template funcs have not become widely shared and people seem to

Go + PostgreSQL. I'm still finding that making the actual HTML part in Go is a bit frustrating. Template funcs have not become widely shared and people seem to deeply entangle them with their own project, and there's a lack of i18n and l10n too. But... most of what I write lives with little to no maintenance, and this is a productive path to a very stable and easy to maintain code base that with locally vendored dependencies checked-in will continue to be stable over very many years. I wrote a Go API some 5 years ago that has required virtually no changes in all that time (I've rebuilt it with every version of Go and only the 1.0 to 1.1 had a few dependency changes - which were trivial updates). The benefits for me, hugely outweigh the negatives of not having more tooling for the web side (the API stuff is wonderful already).