Programming

17497 readers

32 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

130

Why Facebook does not use Git – and why most other devs do • DEVCLASS (devclass.com)

submitted 4 months ago by AnActOfCreation to c/programming

64 comments fedilink hide all child comments

Facebook does not use Git due to scale issues with their large monorepo, instead opting for Mercurial.
Mercurial may be a better option for large monorepos, but Git has made improvements to support them better.
Despite some drawbacks, Git usage remains dominant with 93.87% share, due to familiarity, additional tools, and industry trends.

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

[–] Mikina 13 points 4 months ago (1 children)

My best VCS experience so far was when working with Plastic SCM. I like how it can track merges, the code review workflow is also nice, and in general it was pretty nice to work with.

Fuck Unity, who paywalled it into unusability, though. Another amazing project that was bought and killed by absurd monetization by Unity, same as Parsec.

[–] [email protected] 3 points 4 months ago (1 children)

How was Parsec before the acquisition?

I only really have experience after, and it's the only Unity product I've actually found that I like. My only major complaint is that it's not compatible with the base configuration of Palo Alto, but that's really more of a Palo Alto problem than a Parsec problem.

[–] Mikina 9 points 4 months ago* (last edited 4 months ago) (1 children)

I still use Parsec for remote, and I don't have any issue with it, it works great and I like it. However, they also did offer a free SDK (Unity plugin) to integrate remote play into your game natively (just like you can have "Invite to Steam Remote Play" button from Steam SDK), which was exactly what we needed - and Steam Remote was never working without issues for us, in comparison to Parsec which worked amazingly well every time we tried it.

I found numerous mentions of Parsec SDK and how easy it is to integrate, but after Unity bought it, I couldn't find it anywhere. Only mention was that if you need it, you should contact them.

So I did that, mentioning that we are a small team of students working on a offline co-op only 2 player game in our free time, and that since Steam Remote wasn't working for us and I have great experience with Parsec, I asked what we have to do to get access to the SDK/Unity plugin.

Unity's answer? Sure, no problem, they will be happy to give us access, with first step being that we pay them 1 000 000$ for it.

Like, wtf? Did they even read the email? How out of touch you have to be, to casually ask a small student team to pay 1 000 000$?

[–] [email protected] 3 points 4 months ago

Okay that's fair. Their pricing is awful in general, and that's especially egregious for something that used to be free