okay so swarm is dead, but is kubernetes actually that good or is it just ubiquitous and you’re forced to use it today? what about nomad? or mrsk?
k8s is good, I don't get the hate against k8s.
Docker
41–50 of 145 posts
Re: Docker
#42I know I will get downvoted for this as off topic, but this is just the latest blog we've seen in this top 30 of many that show ZERO regard for legibility. Yes, I can zoom my browser, but c'mon. A 13px font for paragraph text is nearly hostile. It's not that legible to people with perfect eyesight, but then it's not at all legible to anyone with imperfect eyesight. It's like saying you don't care if anyone who reads…
I agree, at least with Firefox we can put in read mode, in this case it was much better.
Re: Docker
#43Earlier quoted context omitted.
(author) I'm not sure that we really disagree, but I wrote this sort of late and I also think I wasn't entirely clear. The point I was trying to make is that the "container runtime" part of Docker is a lot less important than the tooling they put around it, and they made Docker Hub a very core part of that broader ecosystem.
I think that in many ways creating a shared, stable namespace for images was actually a bigger contribution than any of the technology. The ability to type somtething like 'FROM python:3' at the top of your Dockerfile and have that automagically mean what you expect was definitely revolutionary in terms of productivity. Behind the scenes I don't know it really matters that much whether that references an image hosted…
Namespaces are so important to ecosystems. See the issues with NPM packages, discussions about Cargo organisation names, etc. I was a huge fan of Deno early on because it used "the web" as its package namespace. Every time I see a new tool come out which bakes an assumed default into a "bare name" I die a little.
Re: Docker
#44In its weird death spiral, if Docker Inc. were to be bought out by Microsoft, I shudder to think how much of the dev ecosystem would yet again depend on Microsoft's good graces to shoulder the burden of storage and data transfer costs for building products. They already do npm and Github (+ Github Container Registry) so they have some standing in being stewards in this space.
On the plus side, it would perhaps give enterprises more confidence about their build pipelines remaining dependent on Docker Hub, maybe even being more comfortable paying for it.
On the flip side, far too much of the dev ecosystem would depend on Microsoft, the famed supervillain of open communities. EDIT: With that sense in mind, I am indeed rooting for Docker Inc. to succeed.
Re: Docker
#45I think we're past the point where key players like AWS have _ran with_ the technology Docker provided and did not pay their fair share in the process. Docker as a company may be a joke, but I don't think the software will be nearly as nice to use without them. I think it's ridiculous that so many asshats are jumping on the hate Docker (the company) bandwagon without understanding how much they have been taken advant…
> Docker as a company may be a joke, but I don't think the software will be nearly as nice to use without them. I think it's ridiculous that so many asshats are jumping on the hate Docker (the company) bandwagon without understanding how much they have been taken advantage of by the big players who can absolutely support them, but choose not to. As much as I do not condone said big player's actions here, the whole sy…
Yep. Hate the game, not the player.
Re: Docker
#46The narrative seems quite clear to me. They released the tooling and the services to become the defacto solution, and then Swarm was supposed to be the cashcow that turned that into cashflow. And then k8s happened. They've raised a tonne of capital, and it probably looked sane at the time. And now they're grasping at straws trying to figure out how else they can turn this into revenue. A lot of the recent narrative h…
It always seems like VCs. They did great and started growing a lot. More VCs jumped into the next possible “unicorn” and they had even more money. They had to do stuff with it. But they weren’t paying back fast enough, and K8s was making waves. Better make money fast while you can. Time for the squeeze play so the VCs can win. If they had been allowed to grow at a more natural rate maybe it would all be fine. If they…
[deleted]
Re: Docker
#47How does the Docker story compare to NPM who are also freely hosting a bunch if stuff, heavily downloaded and relying on some paid users but mostly free. And NPM has “competing” repositorys too. Could the same happen with NPM where they need to charge?
I get that NPM packages are smaller than docker images typically.
Re: Docker
#48okay so swarm is dead, but is kubernetes actually that good or is it just ubiquitous and you’re forced to use it today? what about nomad? or mrsk?
k8s is good, I don't get the hate against k8s.
k8s is good, but complex, and thus not fit for everyone and everything, but gets overused to death due to being the most popular choice, thus you have a lot of people that dislike it due to bad experience.
Re: Docker
#49okay so swarm is dead, but is kubernetes actually that good or is it just ubiquitous and you’re forced to use it today? what about nomad? or mrsk?
Nomad is awesome and works at scale. The engineers continue to battle harden it and it’s a joy to work with. You do have to manage things like service discovery (usually with consul) and traffic routing separately - but the integration with vault is sublime. About the only real negative of Nomad is that it doesn’t have the mindshare that k8s does, so you don’t see the amount of developer engagement in extending it th…
> You do have to manage things like service discovery (usually with consul)
Since the last couple of versions there has been native Service Discovery in Nomad which works pretty well.
Re: Docker
#50The narrative seems quite clear to me. They released the tooling and the services to become the defacto solution, and then Swarm was supposed to be the cashcow that turned that into cashflow. And then k8s happened. They've raised a tonne of capital, and it probably looked sane at the time. And now they're grasping at straws trying to figure out how else they can turn this into revenue. A lot of the recent narrative h…
> then Swarm was supposed to
> be the cashcow that turned
> that into cashflow. And then
> k8s happened.
We are still using Docker Swarm in production. It seems to be working fine so I always wondered why it never took off. But I am not a Devop. Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?