Docker is a dangerous gamble
I don&#x27;t disagree that deploying Go or Rust apps (I think the author is wrong to include JVM in that bunch) is much nicer compared to ones where you rely on shared libraries system-wide, and may even remove the need for Docker.<p>However, I think the author trivializes the amount of work required to make different types of Python&#x2F;PHP&#x2F;NodeJS&#x2F;whatever apps all work in a consistent way through configuration management, saying &quot;I can just write a bash script or makefile.&quot; or &quot;just download roles from Ansible Galaxy&quot;. This is so painfully ignorant and irresponsible that I fail to take the article seriously as a whole.<p>Even if it&#x27;s just a Jenkins job doing a docker pull &amp;&amp; docker run I&#x27;ve still seen massive improvements in the maintainability of configuration management code because there are so many fewer edge cases you have to take care of. No K8s required for that.<p>The author, writing about languages like PHP and Python (and I assume NodeJS becuase it also works in a similar way, but he doesn&#x27;t explicitly mention it for some reason):<p>&gt; They arose from an old paradigm, which is not suited to a world of microservices and distributed computing in the cloud.<p>So just because they can&#x27;t build a single static binary, they&#x27;re not suitable for microservices and distributed computing. Got it...<p>&gt; If the switch away from Ruby&#x2F;Python&#x2F;Perl to a newer language and eco-system allows you to achieve massive scale with less technologies and less moving parts, then you absolutely have a professional obligation to do so.<p>Wow it&#x27;s that easy?! Be right back, re-writing all our code in Go over a weekend hackathon.<p>This article made me angry.