I would like to share with you Sturdy - a new, real-time version control platform, specifically made for work. Pull requests were designed for an open source workflow, and I think tooling can be way better in a team setting (eg. folks that do standup, planning together etc). The core ideas of Sturdy are: 1. High-level operations around developer intent 2. Early feedback (like pair-programming) which is also given asynchronously (like pull request reviews) 3. Compatible with existing tooling On the website - https://getsturdy.com/ there are some short clips of how it works. It's pretty easy to try out, I would love to hear what you folks think. Sturdy is itself open source - https://github.com/sturdy-dev/sturdy (stars welcome 🙂 ). Cheers!

I had a quick look at the Web site, just reading from top to bottom. But I still have no idea what Sturdy does differently from git. Statements such as "Sturdy maps developer intent to concrete actions." sound interesting but provide no hint at all at how this translates to an implementation.

Is that first video how you'd use it? Every few keystrokes, when you have an atomic change, your pair reviews and merges it into their copy?

Thanks @Konrad Hinsen and @alltom for this feedback, it's truly valuable. Communicating concepts is definitely a challenge of its own, and frankly, I find it difficult. I have just deployed a new version of the site, which tries to "Show, instead of tell", without resorting to a video. I would be super thankful if you could share your opinion on the new presentation! 🙏

Good work @Kiril Videlov, that's a lot clearer. Someone who knows the standard GitHub workflow can well see the differences, and even imagine how Sturdy does it behind the scenes.

I think I understand it much better! It looks like having your workspace be mirrored online to make it fast for others to review and merge. That sounds really nice.