Nothing. It fixes the myriad of horrible hacks that are required for ipv4 to somehow still hang on.
Of course companies are sad because transition costs money, even though as usual the open source community did most of the work for them.
I don’t think a lot of people think that mushrooms are vegetables in any sense. If you check culinary lists of vegetables, they don’t contain edible fungi.
Good advice, bad biology: mushrooms aren’t plants and therefore nor vegetables.
But that’s my point: instead of things weirdly not working, they will work instead.
From github’s blog:
git clone --depth=1 <url>creates a shallow clone. These clones truncate the commit history to reduce the clone size. This creates some unexpected behavior issues, limiting which Git commands are possible. These clones also put undue stress on later fetches, so they are strongly discouraged for developer use. They are helpful for some build environments where the repository will be deleted after a single build.
Maybe the hashes aren’t different, but the important part is that comparisons beyond the fetched depth don’t work: git can’t know if a shallowly cloned repo has a common ancestor with some given commit outside the range, e.g. a tag.
Blobless clones don’t have that limitation. Git will download a hash+path for each file, but it won’t download the contents, so it still takes much less space and time.
If you want to skip all file data without any limitations, you can do git clone --filter=tree:0 which doesn’t even download the metadata
I think in this case, “depth” was am inferior solution to achieve fast cloning, that they could quickly implement. Sparse checkout (“filter”) is the good solution that only came out recently-ish
No, don’t do that. That modifies the commit hashes, so tags no longer work.
git clone --filter=blob:none is where it’s at.
It’s pinned and !Unpin, and only has private constructors.
Uploading is a matter of implementing Clone
Yup! All of the following features were in CoffeeScript first: Modules, classes, arrow functions, async functions, parameter defaults, …spread, destructuring, template strings.
So I’d say it was extremely successful in making JavaScript better.
So that “special release build” is the build you do debugging with. Shouldn’t you just modify the otherwise useless debug profile and turn on all the optimizations necessary to make it usable?
Surgeon simulator. The funniest video ever
It did, wherever it’s used. If you can ditch backwards compatibility in your network and just use ipv6, everything gets so much simpler.