Show HN: Sturdy – online-first version control focused on collaboration • Hacker News Board

Re: Show HN: Sturdy – online-first version control focused on collaboration

#41

Post by d--b » Sat, Aug 21, 2021, 6:21 AM UTC

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...

Re: Show HN: Sturdy – online-first version control focused on collaboration

#42

Post by zegl » Sat, Aug 21, 2021, 10:14 AM UTC

cutemonster wrote: post #40

videlov wrote: post #36

Earlier quoted context omitted.

Thanks for sharing your perspective. I understand the point of formalizing contributions but wish to challenge the need to do so for every type of contribution. For instance changes that have low impact production (eg. clarifying documentation) are subject to the same process as high impact changes. We are experimenting with an idea where depending on configuration + heuristics (file, author, semantics of change) the…

> We have been using Sturdy in it's own development I'm wondering, if one person has some edits in progress (which won't compile), and another person wants to compile and run the app, then, does s/he need to wait for the first one to be done editing?

Nope! Sturdy never syncs edits from one computer to another directly. Our analogy with Google Docs might be falling apart a bit here.

We're working in separate workspaces (which you could equate to a branch), and are syncing and sharing the workspaces only when the code is in a good state.

Re: Show HN: Sturdy – online-first version control focused on collaboration

#43

Post by cutemonster » Mon, Aug 23, 2021, 6:13 PM UTC

zegl wrote: post #42

cutemonster wrote: post #40

Earlier quoted context omitted.

> We have been using Sturdy in it's own development I'm wondering, if one person has some edits in progress (which won't compile), and another person wants to compile and run the app, then, does s/he need to wait for the first one to be done editing?

Nope! Sturdy never syncs edits from one computer to another directly. Our analogy with Google Docs might be falling apart a bit here. We're working in separate workspaces (which you could equate to a branch), and are syncing and sharing the workspaces only when the code is in a good state.

Ok, and, a good state -- I'm thinking that means when there are no syntax errors -- I suppose that generally it's not feasible to compile and run all tests.

One way to use Sturdy, that looks the most interesting to me currently, could be to onboard new team members -- maybe fixing some problem in their first contributions, while they see the fixes happen real time and can ask questions