[533474]

He is entitled to his opinion and you may be breaking the rules of HN by starting a flame war. Our technology is built upon the foundations from our predecessors. I am younger too but I do not promote ageism that is so rampant in our industry

[horsawlarway]

His opinion is misinformed and ignorant of the reality of hosting open source applications.

If you want to host your own blog... sure, run a local copy of nginx or apache.

That's not what this conversation is about. We're not hosting our own websites - we're replacing crappy ad driven/subscription SaaS companies with open source applications, running on our own hardware/networks.

The use case there for containers is both obvious and compelling, and his comment shows that he has zero understanding of the space. So he's making an uninformed rant while talking about the "good ol' days" when everything was SO simple.

Will Docker, specifically, be around in 20 years? Who gives a shit.

Will the concept of an isolated & preconfigured runtime environment (containers)? Fuck yes it will.

[Handytinge]

> The use case there for containers is both obvious and compelling, and his comment shows that he has zero understanding of the space.

I think this is more reflective of you, than him.

The technologies he's discussing drive (often in a poor, bloated way) most containers, and are the underlying components. Learning to self host with containers is fine until you want to customise beyond the ENV variables, or fix a bug and not have to wait on the maintainer, etc, etc.

Containerisation _is_ a recent tech, and it sticking around in the future _is_ debatable. I'm old enough to recall Red Hat (not EL)/Fedora kickstart being the thing that will never be replaced.

The thing that likely won't go away is the underlying infrastructure (nginx, apache, etc) that are worth knowing if you self host.

[r1ch]

You're making a lot of assumptions here. Of course containers will be a thing, I'm not arguing against that and I run plenty myself. My point was that for simple tasks, you don't need to immediately jump into a technology you might not necessarily understand or won't be around in the future. Start with the basics and understand the core concepts.