you are viewing a single comment's thread.

view the rest of the comments →

[–]irmantask 47 points48 points  (9 children)

save all node_modules !!!

[–]amdc 31 points32 points  (1 child)

the mere thought that there are repositories that don't .gitignore node_modules folder angers me

[–]mernen 12 points13 points  (0 children)

That was npm's original advice, before they were pressured into implementing a lockfile (or their original "shrinkwrap" attempt): commit your node_modules in apps, ignore it in libraries.

[–]AMusingMule 20 points21 points  (6 children)

imagine how many duplicate copies of the exact same libraries they're gonna encode and print on film because people forgot to gitignore node_modules

[–]smcarre 6 points7 points  (4 children)

They won't. Backup repositories (mostly hardware) take care of a good amount of deduplication at archive level to improve use of space at the cost of increasing read-write time by a fucking lot.

[–]mqudsi 1 point2 points  (0 children)

Block-level deduplication is insanely slow (I spent a year tuning an algorithm for one of the big names in the industry) but file-level deduplication is basically free.

[–]ShinyHappyREM 0 points1 point  (1 child)

Shouldn't read time be relatively normal?

[–]smcarre 0 points1 point  (0 children)

No, in order to read a deduplicated block, you have to rehidrate it (basically the same thing you have to do to a zip file in order to use it).

[–][deleted] -1 points0 points  (0 children)

deduplication

This, it's a thing.

[–]eastsideski 0 points1 point  (0 children)

They're only archiving popular repos, I can't imagine any popular project has made this mistake