361–370 of 454 posts
Quite hilarious that this guy's motto is "I help high-tech companies cross the chasm by making their products easier to use and learn" http://www.joaofn.com/about/ He is doing quite the opposite
I think we should avoid commenting about the dev's background. It was clearly a company decision and the discussion should be at that level.
I get it. I hate login-walls too. The level of toxicity in the github issue's conversation is so astounding that I must say something. People on the internet are people. I hope that we don't talk to people in "real life" the same as we do when we make toxic comments online. Complain, write letters/emails to Docker, make your opinion heard, etc. But remember that you are dealing with a fellow human-being, who has thei…
One person called the company "jerks" without singling anyone out. Another posted a rage meme to express their displeasure. The overwhelming majority of the hundreds of comments were even more restrained.
Perhaps I'm missing some of the more "choice" comments but as a whole I have far more of a problem with the official corporate-speak than the reactions too it.
Earlier quoted context omitted.
Stuff like this makes me feel better about focusing on Ansible Container instead of Docker. You can use it to create multiple different types of containers without being married to Docker itself.
> First, Ansible Container builds its Conductor container. This may involve pulling the Conductor base image from the Docker Hub registry. Sounds pretty married to me. See https://docs.ansible.com/ansible-container/getting_started.h...
Would it kill companies to be honest and upfront about these sorts of issues? I feel like "Hey, we're unable to pay our bills unless we can better monetize our product" comes across a lot more honest and trust-worthy than this "We're improving user experience! Trust us!" pride-and-accomplishment nonsense that everyone keeps regurgitating. We're not preschoolers, the Internet can spot marketing slogans a mile away.
In Docker's defense they don't really barrage you with marketing. This isn't a situation where if you create an account you're going to get emailed every day about "5 tips on moving your Enterprise application to Docker!". I've had a Docker Hub account since Docker Hub was a thing and the only content I really ever get from Docker is a weekly newsletter (which you can opt out of) and notifications about the platform…
Although they may not barrage you now, there is no telling what the future holds with stunts like this.
Earlier quoted context omitted.
Does offering the source not qualify as offering something? What is the closed source company offering that you are ok with giving your email away? Really an honest question. I find Docker useful, and was put back also by the email/ login request, but why are they getting so much hate, compared to every other company, just because of this?
Because a closed-source company is open about being a for-profit commercial entity that is trying to make a dollar first and foremost. Docker is "revolutionising infrastructure" or something. It doesn't have "make heaps of money" as it's primary goal. Partly this is because open source. There's an expectation that open source is also "for the greater good". The cardinal sin of our times is hypocrisy. Being a money-wo…
This was a bad marketing-driven move, but that's all it is.
If you're frustrated with Docker's slow pace of development are are looking for a good alternative, have a look at Singularity containers. They're interoperable with Docker Hub and OCI compatible images, and offer a much better experience for HPC, machine learning and big data environments. Their GPU support is top notch. They don't run on as many platforms as Docker, but are aiming to grow into cross-platform. Sylab…
Your repetition repetition of "their gpu support is top notch" reminded me of Florida man Marco Rubio in those 2015 presidential debates.
I get it. I hate login-walls too. The level of toxicity in the github issue's conversation is so astounding that I must say something. People on the internet are people. I hope that we don't talk to people in "real life" the same as we do when we make toxic comments online. Complain, write letters/emails to Docker, make your opinion heard, etc. But remember that you are dealing with a fellow human-being, who has thei…
Yes I agree. We don't know why Docker did this. It's not a particularly helpful thing to do, but it's just not that major an issue. I think many who posted on the Github issue will later regret the tone of their reaction. The treatment of the Docker employee was particularly nasty.
Maybe not to you.
Docker is such a mess. As a tool for building containers its cumbersome, has bizarre and frustrating limitations and has issues that haven’t been addressed in years. You can’t use semver for tags, it eats up all your disk space and you have to manually GC it, etc… Multi-build support is basically useless and invariably you end up writing convoluted bash scripts to get the thing to work. Caching is terrible pretty muc…
I like the concept of containers as a lightweight alternative to virtualization. I even use containers (FreeBSD Jails, specifically) for some particular use-cases where I need stronger isolation than separate UIDs, but don't need a full-blown VM. I don't mind this use-case at all.
I really dislike the reality of containers which seem to be "Our deployment procedure and dependencies are so insane so there is no hope of packaging this as an RPM or DEB, so here's an entire userland for you".
As an example of papering over a crazy deployment/dependencies nightmare: I remember seeing a project[0] which used four Docker containers to apply some machine learning based automation to Hue lights. Two of the containers are basically infrastructure pieces (RabbitMQ and Cassandra), one container was dedicated to the machine learning piece and one acts to tie the other three together.
I have no idea why this project needs to run four separate operating system instances to do this job. If I were building it I'd do it as one application, so no need for RabbitMQ, and I'd use an ORM to let the user choose which database is most suited. I'd have an SQLite database as a reasonable default. Maybe I'd have an option to publish stuff to some kind of message queue so that it could be consumed by other systems.
Don't get me wrong, I love the idea behind this project and want to try it out, but it really feels like the author went container-crazy because they could and didn't stop to think about whether they should.
Earlier quoted context omitted.
Because a closed-source company is open about being a for-profit commercial entity that is trying to make a dollar first and foremost. Docker is "revolutionising infrastructure" or something. It doesn't have "make heaps of money" as it's primary goal. Partly this is because open source. There's an expectation that open source is also "for the greater good". The cardinal sin of our times is hypocrisy. Being a money-wo…
What does being open source and being altruistic have to do with each other? Personally, I think they enabled the login, so that new users would be able to use docker cloud, after installing docker, without needing to create an account. But still, being open source, allows you to verify security, be transparent about the product design/intentions, possibly extend or customize for your needs, etc. There is a lot of va…
Would you spend time out of your day to contribute to software that requires your users to sign up for someone else’s spam list?