>>2437fuuuuck. that, plus this insanity
>>2433 Docker should've just been a way to configure linux builds, plus a way to vm it locally. What's the point of spinning up a machine only to spin a new machine inside it. Makes no sense.
Kubernetes might be useful, but it seems like container software's fetish is BDSM, it likes to torture users with shit documentation, so I wouldn't fucking know.
Talking about shit documentation, FUCK aws, especially all that terraforming bullshit.
Mix it all together and you get a bullet to your brain.
untyped dynamic made-in-two-weeks javascript using 3 libraries which somehow made your node_modules folder be 1.6GB
non-deterministic npm builds because fuck you. good luck trying to debug why docker isn't caching your npm build and having to rebuild a huge dependency you don't even use (why does this accent parser library depend on ChartJS???).
oof, then find through the billion articles how to deploy a container on aws. There must be a pre built solution or at least a good tutotial, right? no, fuck you.
oh but now you need a worker (or you bought into the microservices bullshit). motherfucking good luck making your containers talk. how sure are you about your topology now? are they in the same server or are they in a LAN? how many servers are deployed at the moment? can you ssh in or retrieve logs somehow?
fuck kubernetes, don't even want to know what it does.