Have a problem? Put it in docker. Now you have two problems.

@retoor docker went all corpo, no more open source

oh.... it's my favorite

@kiki yeah, planning to jump ship to podman when I can prioritize.

but now you have a containerised problem, and can offload it to the ops team.

also: retoor is right - skill issue.

@retoor Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open source projects.

@retoor why screenshotted? are you that desperate for my approval that you see it as a badge of honor when i agree with you?

@retoor I still remember how you called him “too German to function”, and that was way too sick of a burn

@kiki what do you mean it went all corpo?

Fuck that shit!

Edit: I read the whole thread now! It was good while it lasted!

@retoor well, if you want me to agree with you more often, you just have to be right more often, young lady ;)

@retoor we already have a way to package code and its dependencies into a reusable package. It’s called a binary.

@kiki docker is not for "packaging code", but for "packaging a service", with the code being just one part of the package.

@tosensei what’s the difference between code and service then?

@kiki static assets, configuration, dependencies...

you're basically asking "what's the difference between a cake base and a cake", or "what's the difference between an engine and a vehicle"

@tosensei configuration is code. static assets aren’t being put into docker in the first place. dependencies are bundled with code.

@tosensei I’m afraid your analogy isn’t quite right. If code is engine, then docker container is everything but engine. I can engine-swap a car, but I can’t code-swap a docker container. Motorcycle engine inside a car still gives you a functional car. If the car is light, you can use a lawnmower engine, or even a chainsaw engine. There are cars that run on piston airplane engines.

An image upscaling AI’s code inside a docker container that was made for compiling an OS gives you a non-working mess that doesn’t make sense.

@kiki ...if you put a motorcycle engine in a car, you'll have a shitty car. if you put a tank engine in a plane, you'll have a shitty plane. if you put a [use case X] binary in a [use case Y] container, you'll have a shitty container.

i assumed a modicum of common sense when providing my analogy. it was obviously about the scope of the components, not about interchangeability.

but your example of putting an image AI into a dev-tool container would be more analogous to putting a lawnmower engine inside of a dog.

@tosensei well, a dog with its heart swapped with a pump powered by a lawnmower engine is such a cool idea! wake up bro, it’s time to supercharge our dog!

@kiki lanwmower engines are usually two stroke. those don't work well with supercharging/turbocharging.

don't you know anything about canine anatomy?

@tosensei nah, but I know that there are portable heart pumps for humans. No, not pacemakers, a legit pumps. You gotta carry it in a bad with you though