4 ms·
Sorry about it, we rushed a bit the last update and introduce a severe bug. But the whole goal of auto-upgrading is to avoid the spread versions Maybe you wou
by userbinator 6y ago
Sorry about it, we rushed a bit the last update and introduce a severe bug.
But the whole goal of auto-upgrading is to avoid the spread versions
Maybe you wouldn't have so many versions if you slowed down and actually took the time to make sure each version you do eventually release was more stable...?
With a lot of "modern" software, I feel like it's not just "move fast and break things" anymore, it's "keep moving and breaking things". In particular, certain types of software like browsers and OS invoke feelings of dread upon each update: "what did they break/what user hostile crap or other unwanted changes did they try to sneak in this time?"
Docker is, like a lot of other software, "foundational" in that its error-free operation is relied upon by many. How can developers build anything reliable if the foundations are shaky?
Maybe that's partly why retrocomputing is so popular. With something like a C64 you never have to worry about the platform changing, so you can spend all of your energy on solving the problem you had in mind, instead of the ones created by the platform trying to shift under you.
- edoceo 6y agoIt's like we learned nothing from web-framework churn and decided to go levels deeper. This time will be different (tm)
- alpaca128 6y agoI don't know how developers can look at the mess Microsoft causes with forced Windows 10 updates and think it's not only fine but they need to add another layer so that when the OS auto-updates without asking it might kick off a chain reaction of user applications wrecking themselves recursively. At least we don't have to worry about a Skynet I guess.
- 60secz 6y agoMove fast and break everything. Some version spread is desirable.
- rlayton2 6y agoGreat points. "Move fast and break things" is for new companies that don't have people relying on them. People who use this saying to keep moving forward should be aware of the fact that Facebook no longer use this (). I've heard "Move fast with reliable infrastructure". In other words, Facebook invest massive amounts of money to allow them to test and deploy new features without breaking the whole site. If you don't want to make that investment, you don't get to move fast without breaking things. I'm not in Facebook, above information is from a podcast. If you are from Facebook, I'd love your input
- jhanschoo 6y ago> Maybe you wouldn't have so many versions if you slowed down and actually took the time to make sure each version you do eventually release was more stable...? Considering that containers and orchestration is still a rapidly changing field I disagree with this assessment.