I've seen that, but I've also seen individual engineers and entire departments refuse to move on from what they are using. When they eventually realize they need to change, they are a lot further behind than they were initially, and it takes a lot more work to catch up.
A lot of organizations are getting real value out of Docker (and Kubernetes and NoSQL and React and all of the other trendy new things), and saying that "no one needs it" is just as myopic and wrong as being part of the herd mentality.
At the risk of nitpicking a word that may have been just used for emphasis, how can you be sure the value is real, though? Perceived value can be tough to tell apart, especially in a monoculture (called "herd mentality" earlier, perhaps too uncharitably).
Also, even if the value is real, is it technical, or political/behavioral? If it's the latter, that doesn't minimize theri value, but let's not pretend their advantages are technical. We could, instead, discuss if using the new tool is the best (or only) way to effect that change. It may be. It may even be that which tool it is doesn't matter, so long as it's different, as has turned out to be the case in ergonomics and RSI.
We've certainly seen some negative "NoSQL" headlines. How many startups used it to their eventual detriment, just following a trend and/or doing premature optimization? I'm not saying it can't provide value, rather than mere popularity and even perceived value, especially initially [1]
> saying that "no one needs it" is just as myopic and wrong as being part of the herd mentality.
I think that's what's called a "shallow dismissal" and is discouraged by the guidelines. The bare statement would be mere hyperbole and could possibly be "just as" wrong, but it was in reference to an entire article, which lays out the technical reasoning, which it's up to you to refute and point out they myopia of.
[1] I am reminded of how "easy" MySQL replication was always touted to be.. except that people choosing it did so with an empty database. If it broke, with a far-from-empty database, I found myself wishing for one of PostgreSQL's much more "difficult" options.
It might be simple for an adept developer but not all companies can find/hire that kind of talent. You need abstractions that simplify dev ops in a way. Yes, docker does not solve everything and should only be used when you can leverage some of its pros.
Not sure I agree with the conclusions. A bunch of OS-specific alternatives don't compare as I see it, but regardless, for me the value of Docker isn't the filesystem trees alone but the tools that then leverage them; compose, swarm, etc.
It's this kind of gross exaggeration that's keeping AWS so profitable, I suspect. Half a year and 5 sysadmins for only 100 server would do the NYC MTA subway construction team proud.
> We have to minimize time to market, make money not build servers
This is a false dichotomy, though. Of course you'd start with something where you can have infrastructure on day 1 of product launch. At small enough scale, cloud (or a VPS) is actually cheaper, too. Once you're at "time to market", if you're not re-evaluating, I'd say that's foolish.
> make markup adjusted with price
I'd expect any business to prefer to keep that markup for themselves as profit, assuming they even have that pricing power in the first place.
Running a server is child's play, people. Don't believe the hype!
I've done this analysis for (mostly small-scale) companies for about 10 years, and, every time, the cost of using public cloud computing has been 2x-10x of running ones own servers for 3 years.
I've only had one exception, where the incremental cost of compute was 1:1, if the servers were placed in more expensive space near the other servers in the existing datacenter. Data transfer costs made cloud more expensive, of course.
> Running a server is child's play, people.
I'd say that's a bit of a hyperbole, but I agree that the incremental expertise (and time/effort) required to deal with hardware over cloud, is far from the prohibitve headache it's made out to be.
But I (and the GP) addressed that. It just isn't hard.
Your earlier comment is closer to the truth:
> political and cognitive effort of doing it themselves
With "traditional" industries, it seems the problem is entirely political, and it actually is about cost, because cloud isn't competing against the commodity gear we've been talking about here. Cloud is competing against "enterprise" hardware, which easily costs even more than cloud, not least of which due to maintenance contracts.
There was some discussion of this (somewhat tangential to the main topic) I participated in here https://news.ycombinator.com/item?id=17329028
I have servers in the data center and in the cloud, and I can say that the line "is exponentially more cost effective than any cloud service" has so many caveats attached, it's not even worth debating.
Simply put, if all you are doing is comparing running X servers in the DC and running the same servers in the cloud and that's it, yes, the cloud will be more expensive. This is why no cloud provider recommends simply doing that.
> People are not doing their homework
You should continue to do homework.
Only thing I'll add is that at best it's asymptotic to a constant factor more cost effective.
I found this article from Saturday worth the read, as it explains what Docker actually is, and why no one needs it: http://catern.com/posts/docker.html.
The same goes for everyone working in the cloud; I've build my own clusters to compare the effort and expense (rather than just accept the marketing line) and running one's own servers, from one to hundreds, is exponentially more cost effective than any cloud service.
People are not doing their homework, and the herd mentality owns the entire tech industry.