3 ms·

This article failed to mention the most important thing: An actual advantage of fat binaries. The closest he comes is saying that he feels the docker way is "ol

by luord 9y ago

This article failed to mention the most important thing: An actual advantage of fat binaries. The closest he comes is saying that he feels the docker way is "old"... As compared with fat binaries, which is how desktop applications have been shipped for decades. Hell, size, the only clear would-be advantage, is only mentioned in a throaway sentence. > Yes, the network can be very powerful, but trying to use it for everything is a royal pain. He says this after saying docker is unsuited for the massive scale of microservices... Where everything communicates through the network anyways. Also I have a feeling he doesn't know the distinction between kubernetes and docker. They don't actually compete with each other, I don't even understand the comparison. Kubernetes uses docker. All in all, I'm not convinced. PS: At least in python, there are ways to create fat binaries anyway. And I have no doubt that this guy is very good at operations, as he seems to have not found problems with go's dependency management and even implicitly compares it favorably with those of the scripting languages.

pmoriarty 9y ago
"I have a feeling he doesn't know the distinction between kubernetes and docker. They don't actually compete with each other, I don't even understand the comparison. Kubernetes uses docker." Docker (the company) is itself responsible for this confusion. They're redefined what "docker" means a whole bunch of times.
- curun1r 9y ago
  I had this discussion [0] with their CTO a while back and, suffice it to say, there's a profound lack of understanding of what early adopters like me had to do to lobby for the use of their products in enterprises. [0] https://news.ycombinator.com/item?id=13775732 https://news.ycombinator.com/item?id=13775732
y0y 9y ago
> They don't actually compete with each other, I don't even understand the comparison. Kubernetes uses docker. Kubernetes is scheduling and orchestration. It does compete with Docker, the company - it's a direct competitor of Swarm. Docker, the container technology, is the de facto standard container at this time. That may not always be the case. Kubernetes is not Docker-specific, thus his mentioning of the open container initiative. They are absolutely competitors.

by luord 9y ago

pmoriarty 9y ago

"I have a feeling he doesn't know the distinction between kubernetes and docker. They don't actually compete with each other, I don't even understand the comparison. Kubernetes uses docker." Docker (the company) is itself responsible for this confusion. They're redefined what "docker" means a whole bunch of times.

curun1r 9y ago
I had this discussion [0] with their CTO a while back and, suffice it to say, there's a profound lack of understanding of what early adopters like me had to do to lobby for the use of their products in enterprises. [0] https://news.ycombinator.com/item?id=13775732 https://news.ycombinator.com/item?id=13775732

y0y 9y ago

> They don't actually compete with each other, I don't even understand the comparison. Kubernetes uses docker. Kubernetes is scheduling and orchestration. It does compete with Docker, the company - it's a direct competitor of Swarm. Docker, the container technology, is the de facto standard container at this time. That may not always be the case. Kubernetes is not Docker-specific, thus his mentioning of the open container initiative. They are absolutely competitors.