3 ms·

Consumers often mistake hasn’t changed for a commitment to never change: any sufficiently large product will be littered with these kind of implicit commitments

Consumers often mistake hasn’t changed for a commitment to never change: any sufficiently large product will be littered with these kind of implicit commitments made by the product to consumers that nobody has visibility into. You’re unfortunate that we were all relying on this commitment you’ve never made, but the quick reversion is the best we can hope for. People will theorise how this could have been avoided but c’est la vie — easy mistake that you’ve responded well to.

VWWHFSfQ 4y ago
At this point they'll be stuck on old git for all of eternity unless they just roll their own archive/compress step out of band so the old hashes still work. Yikes.
- groestl 4y ago
  They could also brownout the implied contract over a longer timespan.
  - jeffbee 4y ago
    They could use the old behavior for archives in which all the inputs predate the changeover.
- rfoo 4y ago
  New git has a flag for keeping the old behavior, so it's not as bad.
deleted 4y ago
[deleted]
dharmab 4y ago
Hyrum's Law: With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.
- deleted 4y ago
  [deleted]
- modderation 4y ago
  Incidentally, I'm still waiting for GitHub to implement Spacebar Heating: https://m.xkcd.com/1172/ https://m.xkcd.com/1172/
nickitolas 4y ago
FWIW according to https://github.com/bazel-contrib/SIG-rules-authors/issues/11#issuecomment-1409433084 https://github.com/bazel-contrib/SIG-rules-authors/issues/11... a commitment was made, although in an exchange in some support ticket, and not in documentation.