5 ms·

It feels like an habit of the Docker team, they always try to defend their anti-user decisions with vague and uninspired corporate bs. They're barely trying. An

It feels like an habit of the Docker team, they always try to defend their anti-user decisions with vague and uninspired corporate bs. They're barely trying. Another classic: https://github.com/docker/docker.github.io/issues/6910 https://github.com/docker/docker.github.io/issues/6910

p1necone 6y ago
Wowww: https://github.com/docker/docker.github.io/issues/6910#issuecomment-589179980 https://github.com/docker/docker.github.io/issues/6910#issue... What the hell does "Docker's new direction to go back to its roots and focus on developer tooling" even mean? Docker is developer tooling, that's the whole product. That's not "going back to your roots" that's just doing your damn job.
- aidenn0 6y ago
  Is it developer tooling or deployment tooling?
  - deleted 6y ago
    [deleted]
  - eyelidlessness 6y ago
    I think part of Docker’s value proposition is that it’s both.
- thaJeztah 6y ago
  I wrote that comment at the time; to add some context to that comment: removal of the "login to download" was shortly after the "Docker Enterprise" business went to Mirantis. While Docker started as a developer centric tool, focus shifted to Enterprise products (Docker Enterprise Engine, UCP, Docker Trusted Registry, Docker Desktop Enterprise). After the move of the enterprise products to Mirantis, Docker's focus went back to developer products.
- apple4ever 6y ago
  Oh my I had no idea they actually fixed it! Crazy it took 2 years, but at least they finally did!
- SilasX 6y ago
  Yeah, a lot of times they don't seem to understand that their core product is "you can run this command, and the virtual machine will work on any system that runs Docker, limited only by resource availability". Heck within the first few weeks of dockerizing our system at a startup (c. 2015), they introduced a backward-incompatible change to docker-compose that we only found when onboarding new employees -- the exact thing it's supposed to be for!
microtherion 6y ago
These may simply be issues that are not at the discretion of these developers to either change or discuss with third parties. As tempting as it is to weigh in publicly on such matters, the best way for a developer to get results is often to say little in public and try to resolve the issue behind the scenes (as was apparently done here).
- wmf 6y ago
  The honest way to handle this would be for the CEO to say something like "I made this decision and I accept responsibility for it".
  - eyelidlessness 6y ago
    And the paucity of honesty in public communications is a testament to how few CEOs (and others in a leadership role who could buck-stops-here) are that sincere, willing to take that kind of heat, or to invest in understanding the problem in the first place. It’s also often a testament to how pathologically organizationally shielded they often are; I’d bet money even 5k thumbsdowns on an issue doesn’t bubble up to the top at most orgs.
yellowapple 6y ago
> we've made this change to make sure we can improve the Docker for Mac and Windows experience for users moving forward "How should we improve user experience? I know! Let's ruin user experience by forcing users to signup for an account they don't actually need! Brilliant!"

p1necone 6y ago

Wowww: https://github.com/docker/docker.github.io/issues/6910#issuecomment-589179980 https://github.com/docker/docker.github.io/issues/6910#issue... What the hell does "Docker's new direction to go back to its roots and focus on developer tooling" even mean? Docker is developer tooling, that's the whole product. That's not "going back to your roots" that's just doing your damn job.

aidenn0 6y ago
Is it developer tooling or deployment tooling?
- deleted 6y ago
  [deleted]
- eyelidlessness 6y ago
  I think part of Docker’s value proposition is that it’s both.
thaJeztah 6y ago
I wrote that comment at the time; to add some context to that comment: removal of the "login to download" was shortly after the "Docker Enterprise" business went to Mirantis. While Docker started as a developer centric tool, focus shifted to Enterprise products (Docker Enterprise Engine, UCP, Docker Trusted Registry, Docker Desktop Enterprise). After the move of the enterprise products to Mirantis, Docker's focus went back to developer products.
apple4ever 6y ago
Oh my I had no idea they actually fixed it! Crazy it took 2 years, but at least they finally did!
SilasX 6y ago
Yeah, a lot of times they don't seem to understand that their core product is "you can run this command, and the virtual machine will work on any system that runs Docker, limited only by resource availability". Heck within the first few weeks of dockerizing our system at a startup (c. 2015), they introduced a backward-incompatible change to docker-compose that we only found when onboarding new employees -- the exact thing it's supposed to be for!

microtherion 6y ago

These may simply be issues that are not at the discretion of these developers to either change or discuss with third parties. As tempting as it is to weigh in publicly on such matters, the best way for a developer to get results is often to say little in public and try to resolve the issue behind the scenes (as was apparently done here).

wmf 6y ago
The honest way to handle this would be for the CEO to say something like "I made this decision and I accept responsibility for it".
- eyelidlessness 6y ago
  And the paucity of honesty in public communications is a testament to how few CEOs (and others in a leadership role who could buck-stops-here) are that sincere, willing to take that kind of heat, or to invest in understanding the problem in the first place. It’s also often a testament to how pathologically organizationally shielded they often are; I’d bet money even 5k thumbsdowns on an issue doesn’t bubble up to the top at most orgs.

yellowapple 6y ago

> we've made this change to make sure we can improve the Docker for Mac and Windows experience for users moving forward "How should we improve user experience? I know! Let's ruin user experience by forcing users to signup for an account they don't actually need! Brilliant!"