View Single Post
Old 08-27-2023, 12:48 PM   #18
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
I don't really have anything against Redis & Openresty, they (well, Openresty really) just happen to be slightly more invasive and involved to deploy than a standalone Rust or Go binary (or a Python web app) (especially if you can't/won't use Docker; and both apply here: I'd have to mangle my kernel & systemd configs to even be able to run Docker, while I can pretty much isolate a random binary in a much clearer fashion with a simple systemd unit).
And I'd have to mangle my already custom nginx & luajit ebuilds to just go native with OpenResty, as it isn't packaged in the main Portage tree. And, again, nginx configs.

(And, also, running a whole OS layer in a container, even a slim one, just to run a 5MB daemon doesn't really jive well with me ;p).

Last edited by NiLuJe; 08-27-2023 at 12:54 PM.
NiLuJe is offline   Reply With Quote