I believe the it's over because tech X has thinking is at best lazy and at worst dangerous. It implies that the everyone's requirements are the same and static and that solution X has reached all of those requirements.

If people blindly accepted X has won we'd be still using Perl, XML, CGI-Bin, Apache, Angular, etc. As another comment has said, I believe years from now, folks will be looking back at in disbelief at how anyone could have considered k8s to be the best solution without room for improvement or alternative approaches.

> I believe the it's over because tech X has thinking is at best lazy and at worst dangerous. It implies that the everyone's requirements are the same and static and that solution X has reached all of those requirements.

I'm somewhat inclined to agree, because iterating on what we have and developing new tech and practices seems like a good idea (the concept of 12 Factor Apps comes to mind).

However, I can't help but to wonder what this would look like, when taken to the extreme. Perhaps something along the lines of: "We are only going to use Ubuntu for the servers and Java for all of our back end services, as well as React for the front end. Nothing else, no matter how many different projects there are."

And on a certain level, it makes sense: consistency and skills that carry over seem like a nice thing to have, there's even terms out there like a company being "a Java shop" and so on.

That said, such inflexibility might not always be nice (e.g. trying to do machine learning in Java) but at the same time if a specific technology is in demand in the job market in most companies, you don't really get much of a choice.

To return from the analogy, in the particular case of Kubernetes, you'll have to learn and use it and there's only so much free time for exploring other options.

> If people blindly accepted X has won we'd be still using Perl, XML, CGI-Bin, Apache, Angular, etc

For many folks, some of those might indeed be good choices.

Some backup software that I use is written in Perl and is actually pretty good (BackupPC).

XML can be a nice format to use and has lots of tooling available. Even SOAP wasn't necessarily the end of the world thanks to WSDL - being able to plug a file into SoapUI and getting an API that you can play around with, something that took Swagger/OpenAPI years to reproduce for REST.

There's something nice to be said about the simplicity of CGI and FastCGI still makes sense with something like PHP (PHP-FPM).

I actually still use Apache for hosting my personal stuff - if has most of the features you might want and with mod_md it's a bit closer to Caddy than Nginx in getting LetsEncrypt certs (ACME). If you disable .htaccess, reasoning about the config also becomes about as easy as with Nginx (nginx.conf).

I've also seen Angular be used reasonably well and the "batteries included" feel of it was nice, especially when React had about 1500+ dependencies for a new project. I do personally lean towards Vue, though (oh and migrating away from AngularJS after the EOL was a pain, when that was relevant).

My point is that if something is good enough for your needs and helps you put food on the table, then you can just go with that choice.

Let those who prefer to experiment do so (hopefully not with your livelihood), celebrate their efforts and successes and learn from their failures, though. Kubernetes is established, Nomad is interesting, even Docker Swarm or Compose is okay.