Nostr Web Client

This seems to have given way more weight than it should lol.

There are no technological statements behind wearing a T with a cute blue whale. It's nice, it's cool, it's blue, or simply, it might have been the next accessible piece in their wardrobe.

I think some devs need to take a serious break from emacs-vim-style warfronts. I mean, I normally don't care, but it kinda feels sad seeing tech people hitting on each other and think it is funny.

Now back to docker tech, there are people whose job is to ship containers for production, docker or whatever, who cares. It is a thing and they get paid for doing it. Obviously as part of a larger task set; DevOps, SRE, ..., the point.

I'd let them be proud of what they want. Or should I instead tell them, what you do sir is a hack, it is no real tech, don't be proud? What? Why?

freedom dev 𓅦 2y ago

Yes, the shirt doesn't matter. The point is that people like the tech. And that's OK.

I assume Pablo doesn't like it. And neither do I. That's OK too.

And probably this is not the moment to tell people in their face "excuse me, sir, but your tech sucks", but in the future it may happen.

Better tech means a better life for everyone, and the obsolescence of popular bad tech will be worth it.

And I'm not talking of Docker as "a problem" here, rather it's a symptom. It solves a problem that shouldn't exist in the first place. It is a consequence of many decades of bad tech.

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 2y ago

nspawn is better and in the age of ubiquitous SSD the benefits of overlay filesystems, which docker makes easy, are questionable in these days of SSD filesystems and cheap memory

nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h introduced me to nspawn and i wrote some deployments for his relay-tools using bash scripts

dockerfiles are really just slightly souped up specialised bash scripts so nspawn lets you throw out the nonsense and deploy without adding the complexity of the docker engine

don't need root to do nspawn containers - this is a major deficiency of docker

Nour 2y ago

I'll be interested in knowing viable production alternatives to consider for my daily job. Just to try.

The CLI you use won't change much. Every single application out there has a Dockerfile, sorry not sorry xD

With Kube I usually don't care, but it mostly uses containerd as a container runtime. Previously at an enterprise and before they purchased the docker desktop license for us, I used podman.

As of today, and without using SaaS, I'm unaware of how to ship software to production without containers tech.

I'm just here to make a point to Pablo and others. I wouldn't want to interpret the internals of that docker guy and neither going to label him personally (otherwise he is normal).

I think that's a shame if it meant or slightly hinted to "he might be not normal", and for what? Wearing a t-shirt.

Not 🆒