When Microsoft's JavaScript repository was growing faster than Office's, it was clear that something was wrong. A Microsoft engineer explains how the repo
It’s not as stupid as this blog post makes it sound. This was a hashing function that was intentionally taking the end of the path as the most significant part. This just impacts the order of objects in a pack file, and the size of the compression window needed to compress it.
It’s not actually mistaking one file for another, and their proposed solution is not better in all situations.
yeah i’m not saying it is stupid or something, but this kind of optimisation is found in C code very often, where people take the first|last N of something because it is most likely good enough :D
that is such a C thing to do.
It’s not as stupid as this blog post makes it sound. This was a hashing function that was intentionally taking the end of the path as the most significant part. This just impacts the order of objects in a pack file, and the size of the compression window needed to compress it.
It’s not actually mistaking one file for another, and their proposed solution is not better in all situations.
yeah i’m not saying it is stupid or something, but this kind of optimisation is found in C code very often, where people take the first|last N of something because it is most likely good enough :D