Technology

59288 readers

3795 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

Flaw in Git bloated Microsoft repository by a factor of 35. (www.techzine.eu)

submitted 2 weeks ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 34 points 2 weeks ago (1 children)

The algorithm checked only the last 16 characters of the path, so package differences were not considered.

that is such a C thing to do.

[–] [email protected] 27 points 2 weeks ago (1 children)

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.

[–] [email protected] 7 points 2 weeks ago

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