This post has been moved to the Sturdy blog
Hey everyone!
We've been working hard on Sturdy for the past few months, and as you might have seen, we've been making quite a lot of changes. I'm super excited about where we're going, and to be able to show of Sturdy and some of it's internals here in this post.
Sturdy is replacing Git with real-time collaboration in the cloud
Let me tell you how it works!
Sturdy mainly consists of two components, the "Sturdy Agent" that runs on your computer (more on that later!) and the Sturdy website. The website is used for everything that you need to do in your daily workflow, such as describing a change, reviewing a change, and sharing a change with the team. No command like skills or third party GUIs required!
Unlike Git, Sturdy has no concept of remotes (or checkouts), instead all developers on a project are working closer together. Developers are still working separately in what we're calling a workspace (there are no "shared cursors", which you might be used to in Google Docs or Replit). Your changes are synced with the changes of other developers only when you’re ready.
The Sturdy Agent automatically syncs a directory on your computer with Sturdy, when you're making a change it will be automatically synced within a few milliseconds.
Pick the changes that you want to share with the team - in just a few seconds!
The Sturdy agent (the part on your computer)
Sturdy runs a lightweight process on your computer that watches the file system for changes, and syncs it with Sturdy over a SSH-based protocol. If you make any changes to Sturdy via the web, such as switching to a different workspace, Sturdy automatically swaps out the files on your filesystem within seconds.
Sturdy does not require any permissions on your computer, and is easy to setup.
Changes since last time
1. Conflict resolver
Conflicts can happen to the best of us, and can happen even when using Sturdy. When a conflict can’t automatically be resolved, a human needs to step in and make a decision. The conflict resolver is now available for everyone, and is looking great!
2. Create a workspace in the past
From the changelog of your codebase, use the new “New workspace” button to create a workspace based on this revision. This is useful if you want to go back in time and see what a codebase used to look like.
3. Easy open of a workspace on an existing connection
It’s now easier than ever to switch between workspaces. If you’re creating a new workspace (or checking someone elses workspace out), use the “Use on…” button to open the workspace on a connected computer. And if you’re opening a workspace that isn’t used anywhere, a nice and helpful guide will let you open the workspace in no-time.
That’s it for today! We hope that you like what you’re seeing. You can sign up to join the waiting list at getsturdy.com, and I’ll send you an invite soon.
Thanks,
Gustav