@p @Aldis @Big_Diggity @Lance @gabriel @graf @parker @sysrq @tyler @victor
See, when I said I’d piss everyone off, I figured that would do it. Welcome to hellthread! :helllife:
never mess up with me, reverso. you’re wrong. i’m smiling. this is the most interesting thread in ~6.mo. besides i needed break from trying to get my fbi agent to send me nudes
I think you have to have a dedicated guy. If you have a dedicated guy, it’s not as much of a mess but also does not strike me so much as useful.
dedicated operator is necessary for this shvt. if it were easy to manage mk would be running faang-corps. it’s only useful in the sense that many corps don’t understand the concept of simplicity and distributed computing. mostly they shovel container bodies onto the burnpile and yolo-deploy all day long.
the schedulers (k8s/nomad/etc) fundamentally are simple in design. it’s when you layer on abstraction after abstraction of lo-code/no-code dogshvt the problem becomes complex because nobody can troubleshoot 9 layers of helltrash.
Yeah, but you have that problem with any OS. At least you don’t have that problem twice if you’re not downloading containers from Docker.
you do have a point there. the weirdest thing i’ve seen is.
metal-host(insert os here) --> vm(insert vm host os here) --> docker(insert container os artifacts here) --> app stack --> hello_world
maddening shvt all ov it.
Reproducibility is nice; I don’t like how they did it.
nix has lots of problems, maybe i will sideload a chat with you as to what you don’t like as not to start the fist_shake.
thanks for good thread, komrade. :cupofcoffee: time!