2 ms·

Yes, it does. But your comment also misses the conclusion of the discussion: https://github.com/docker/roadmap/issues/183#issuecomment-802018948 https://github.

Yes, it does. But your comment also misses the conclusion of the discussion: https://github.com/docker/roadmap/issues/183#issuecomment-802018948 https://github.com/docker/roadmap/issues/183#issuecomment-80... In the end, seems they are changing course after listening to user feedback. Clearly auto-updating works in some contexts, but not in others, and now we can all learn from it :)

dvt 6y ago
> Clearly auto-updating works in some contexts, but not in others, and now we can all learn from it :) I think the point was that we all knew auto-updating doesn't make sense in the context of developer tools. I'd even argue GitHub Desktop shouldn't be auto-updating. As a matter of fact, VSCode doesn't, and my compilers certainly don't.
- capableweb 6y ago
  Agree. "I was just following a successful model" is not the right way to approach engineering, without understanding the trade-offs and it seems that step was missed when implementing it in the first place.
  - yellowapple 6y ago
    Indeed, "I was just following a successful model" is exactly why software seems to have progressively gotten worse over the years. "Google does it and therefore I should, too!" No, you should maybe - just maybe - consider, you know, talking to your users and asking them what they want for once, and actually listening when they tell you. And this applies outside of software, too. Apple dropped the headphone jack, so guess what every other phone manufacturer wants to do? Samsung shoved ads into its smart TVs, so guess what every other TV manufacturer wants to do? So much for product differentiation.
- eyelidlessness 6y ago
  > As a matter of fact, VSCode doesn't It does by default, using roughly the same method. Gratefully you can turn it off. Edit: gratefully in terms of peace of mind. I’ve only ever been pleased when I do finally let VSCode updates install.
  - dvt 6y ago
    > It does by default, using roughly the same method. Gratefully you can turn it off. Looked over their FAQ, and yeah, I'm super surprised that you're right, I don't remember ever turning it off.
protomyth 6y ago
Auto-updating does not work in any context because you can seriously break the end users stuff with no recourse. It needs to ask, always as you don't know what else is going on.
- capableweb 6y ago
  Well, many people when faced with a question from the computer will be to try to ignore it for as long as possible, that's not ideal either. Opt-out auto-update feels like the right way for consumer software, opt-in auto-update for professional software, like developer tools.
  - eyelidlessness 6y ago
    For professional (and especially tech-oriented) software I think there’s more leeway to ask the user. Prompt on install/first run would probably strike a better balance than opt-in.
willis936 6y ago
Isn’t one of the main benefits of containers that you can set static versions, validate them, and then be able to deploy them with confidence that later changes won’t be used? It’s a shortcut to a known working configuration. I would expect container maintainers to appreciate the value of not updating as soon as its available.

dvt 6y ago

> Clearly auto-updating works in some contexts, but not in others, and now we can all learn from it :) I think the point was that we all knew auto-updating doesn't make sense in the context of developer tools. I'd even argue GitHub Desktop shouldn't be auto-updating. As a matter of fact, VSCode doesn't, and my compilers certainly don't.

capableweb 6y ago
Agree. "I was just following a successful model" is not the right way to approach engineering, without understanding the trade-offs and it seems that step was missed when implementing it in the first place.
- yellowapple 6y ago
  Indeed, "I was just following a successful model" is exactly why software seems to have progressively gotten worse over the years. "Google does it and therefore I should, too!" No, you should maybe - just maybe - consider, you know, talking to your users and asking them what they want for once, and actually listening when they tell you. And this applies outside of software, too. Apple dropped the headphone jack, so guess what every other phone manufacturer wants to do? Samsung shoved ads into its smart TVs, so guess what every other TV manufacturer wants to do? So much for product differentiation.
eyelidlessness 6y ago
> As a matter of fact, VSCode doesn't It does by default, using roughly the same method. Gratefully you can turn it off. Edit: gratefully in terms of peace of mind. I’ve only ever been pleased when I do finally let VSCode updates install.
- dvt 6y ago
  > It does by default, using roughly the same method. Gratefully you can turn it off. Looked over their FAQ, and yeah, I'm super surprised that you're right, I don't remember ever turning it off.

protomyth 6y ago

Auto-updating does not work in any context because you can seriously break the end users stuff with no recourse. It needs to ask, always as you don't know what else is going on.

capableweb 6y ago
Well, many people when faced with a question from the computer will be to try to ignore it for as long as possible, that's not ideal either. Opt-out auto-update feels like the right way for consumer software, opt-in auto-update for professional software, like developer tools.
- eyelidlessness 6y ago
  For professional (and especially tech-oriented) software I think there’s more leeway to ask the user. Prompt on install/first run would probably strike a better balance than opt-in.

willis936 6y ago

Isn’t one of the main benefits of containers that you can set static versions, validate them, and then be able to deploy them with confidence that later changes won’t be used? It’s a shortcut to a known working configuration. I would expect container maintainers to appreciate the value of not updating as soon as its available.