I'm a big fan of single-binary websites like this one which rely on as little dependencies as possible (Small, well-written, auditable libraries). What I've fo

I'm a big fan of single-binary websites like this one which rely on as little dependencies as possible (Small, well-written, auditable libraries). What I've found in the go ecosystem as of the past few years is just this enormous graveyard of projects that didn't really seem to get the zeitgeist of keeping as much as close to the standard lib as possible, and included all the batteries. Now you open those old projects written in such frameworks and the batteries are all leaking all over the place and you got some of the juice on your hand, and the github issues page is just a bunch of people asking if the project is still alive yet. You really don't see that with the ones that kept it as simple as, and relying on as little as possible. My old stuff I wrote like that is still chugging along. My only dependencies to track in this case are go, my webserver frontend (openbsd httpd) and the OS updates. Wow! The applications I've written to this end aren't the kind of thing you can host on github pages, they're really dynamic and do all this image processing or handle tons of money a day. Turns out people throw more money around at stuff like that and this alone justifies the means. Hell I know people who even do this in C or C++. That's right, web applications, usually in even more constrained environments like embedded or for game consoles. They get paid more than me, too.