My 2 cents: as someone who’s helped many new developers get comfy with our big codebase, I find this interesting. Right now I get to see what they’ve done only

My 2 cents: as someone who’s helped many new developers get comfy with our big codebase, I find this interesting. Right now I get to see what they’ve done only after they committed so it’s often not the best time. Being able to watch earlier is a good idea. Now, I don’t think you can keep all states of the code (or history is going to be completely unreadable), so you still need some idea of a commit so that people can state “I’m done”. And then you still need the concept of branches, cause otherwise you pick up people’s changes and they break your copy. So all in all, it should look very much like git. Then, you’re going to have an extremely hard time getting people off git. Maybe, and that’s just an idea here. This could be developed on top of git. Where you’re ide live-syncs your changes to a “.live” version of the branch you’re on. Then people interested could subscribe to that live branch, and would get the live syncs in their IDE. And when the actual commit happens, you can then discard all that happened in the “.live” branch. Probably not the feedback you wanted, though...