Sometimes I resist doing things that are probably sensible, for absolutely no reason, for way too long.
#Proxmox was one of those things. WHY was I doing fully manual libvirt/KVM when I could have been doing Proxmox?
Is #docker one of those things too? I"m actively resisting this one HAAARD right now.
What about #postgres? Also resisting this one. Should I stop using mysql for as many things and opt for postgres instead?
I'm pretty sure this is a #NeuroDivergent thing too.
@theo still prefer mysql and sqlite to postgres, it has some really nice features but I have never found it to be as performant for most function.
docker i'm not against, but dislike because it's technical inefficiency and its really just a bandage to the problem of #butitworksonmymachine=
@i0null most of the things I'm running for my own lab use or out of interest are generally pretty performant just due mainly to their small size, no matter how they're setup.
I've got this new lab server up now, maybe I'll find some kinda service to want to run via docker instead. I'm already storing a bunch of my infrastructure as git repos. There's a whole ecosystem of kinda interesting docker tooling and utilities that I just need to find the right situation to use to introduce myself to and it'll likely all make sense.
I agree though that a lot of it seems like bandages to make things work. One of the things I like about stuff written in Golang is how portable the binaries are. I see some of that in docker too.
@theo I agree, the whole point of the ecosystem is to cater to different use cases.
Analysis of large data sets will be different to complex analytics on data subsets.
My advise would be to investigate the differences and deploy according to use case.
Theo Baschak 
Hacker Memes