31–40 of 245 posts
I mean, the same guy that told me this, also said that the codebase size was about 50 times less than the one reported in this slide, so it may all be pure speculation.
Earlier quoted context omitted.
8 GB is still a lot. Would be interesting to know how much of it is actual code and how much is just images and so on.
Exactly, there's no way they wrote 8GB of code.
Is there a reason why they keep everything in the same repo? Can’t you just split the code across multiple smaller repos?
Earlier quoted context omitted.
Why's it bad to store source code on Git ?
Its not bad, is really nice, but Git has one problem, when you codebase is big, the process takes a long time, imagine git scanning those 8GB every time you do a commit, that is why Facebook was looking to port all their code to another VCS
From my experience, we can bet git is the one that takes the least amount of time
Not hitting the network to check which files changed, for a start
Earlier quoted context omitted.
8 GB is still a lot. Would be interesting to know how much of it is actual code and how much is just images and so on.
The big .git directory is probably binary revisions? Is there any good way around that in git?
Pay attention to the footnote: *8 GB plus 46 GB .git directory
8 GB is still a lot. Would be interesting to know how much of it is actual code and how much is just images and so on.
Someone recently told me that Facebook had a torrent file that went around the company that people could use to download the entire codebase using a BitTorrent client. Is there any truth in this? I mean, the same guy that told me this, also said that the codebase size was about 50 times less than the one reported in this slide, so it may all be pure speculation.
So using torrents isn't foreign to them.
I actually prefer monolithic repos (I realize that the slide posted might be in jest). I have seen projects struggle with submodules and splitting up modules into separate repos. People change something in their module. They don't test any upstream modules because it's not their problem anymore. Software in fast moving companies doesn't work like that. There are always subtle behavior dependancies (re: one module depends on a bug in another module either by mistake or intentionally). I just prefer having all code and tests of all modules in one place.
I thought I had read an article about facebook switching to perforce due to their really large git repo. Were they at least thinking about it? A quick google comes up with nothing but I could have SWORN I read that.