5 ms·
I've spoken to Facebook engineers who work on their internal source control systems, and it was pretty obvious from talking to them that Git wouldn't work for t
by danpalmer 10y ago
I've spoken to Facebook engineers who work on their internal source control systems, and it was pretty obvious from talking to them that Git wouldn't work for their purposes. There is plenty of writing about this topic that explains in some detail why Git is unsuitable, and why Mercurial was a better option for them.
As for the 18k classes in their iOS app, I don't see why this is a sign of bad engineering? I'd expect that a large number of these are auto-generated, for example from Thrift API definitions, and I'd also expect that what we see as users is the tip of the iceberg in terms of the code needed. There's obviously a lot of analytics code, and also I'd expect the resiliency and reliability needed requires much more code than we'd expect.
- mattmanser 10y agoIt's nothing more complex than 100,000s of other apps out there. Yet somehow they managed to create 18k classes? Scale is handled at the back-end.
- throwaway698769 10y agoYou are completely right. As a small-company person who migrated a few years ago to one of the Big Four, I can confirm that almost every time someone tells you about "scale" they are bullshitting you. Most developers on those companies either do not deal with scale at all (anyone dealing with front end stuff) or do so by using abstractions which allow them to ignore scale (99% of developers). But scale sounds sexy so everybody pretends they have something to do with it. And it sounds better than "bloat" which is what they really mean. The other variant of "scale" is "I have this single-computer application running on X hundred thousand servers" or some ambarrasingly parallel problem of that sort. Then they will claim boldly that something that has a 0,0001% chance of happening "happens multiple times a day here" which sounds impressive until you realize that that thing has no impact on the SLA and you get saved by the load balancer so it isn't particularly important anyway. The 1% of people who work on real problems in the area don't need to brag on the Internet about "scale" because they are too busy working.
- Bahamut 10y agoThat's not quite true - frontend has to scale for features.
- mercer 10y agoI can't immediately think of any apps that are just as complex as Facebook's, but maybe I'm just not thinking hard enough. Could you give me some examples (honest question)?
- nailer 10y agoUnreal Engine.
- Psilidae 10y agoBased on their documentation—which, albeit, I know has many classes omitted—Unreal Engine has ~6900 classes. That number probably gets greatly multiplied, though, if you count generated classes.
- nailer 10y agoAnd it's managed in git.
- bluesilver07 10y agoI can't find the link, but I remember an Epic engineer saying that they use Perforce internally and do a 2 way sync with Github.
- richardboegli 10y agoCorrect, it is managed in Perforce and MIRRORED onto Github.
- bluesilver07 10y agoI'd think that the Google+, Google Photos, the Twitter apps are at at least 75% of the complexity of the Facebook app.
- mi100hael 10y agoAuto-generated code shouldn't be checked in.
- danpalmer 10y agoI believe the 15k number came from decompiling the binary, not from looking at source control.