[slackstation]

This seems like the product of alot of hard work but, ultimately, who needs this? It's not quite fast enough for pair programming.

There are other faster, free, high quality options for pair programming.

The features of one click deploys and rollbacks tie the deployment system to your proprietary closed-source service.

Retraining a team away from PR and Merge Requests would take time for something that doesn't seem to offer much in the way of new benefits.

Do I have to log into a website to create / switch branches? How do checkout code? Do I download a zip from a website and then click a sync button on my IDE? Am I forced to use VSCode for integration or can I use VIM/EMacs?

[videlov]

Hey, thanks for sharing your thoughts! Co-founder of Sturdy here. We are focused on teams who work closely together and iterate quickly. People often want ship small incremental changes to production. In those cases we found there is a significant overhead of creating/reviewing/merging Pull Requests. At its core Sturdy is about allowing early and continuous feedback in asynchronous collaboration.

The equivalent of switching branches and checking out different code all happen in the webapp. On your computer you get a two-way-synced "magic directory" where you code with your existing tools/IDE/editor of choice. This means that if you wish to checkout someone else's work, a click in the webapp would instantly swap the content of your project dir.

[cutemonster]

> would instantly swap the content of your project dir

How does this work, if the differences between two branches are huge? Say, tens of megabytes. And the Internet connection not that great. If switching back and forth between branches, is there a local cache or does everything (all differences) get downloaded each time?

[iddan]

Sounds like it would be much nicer if you had a plug-in to the IDEs to make the interaction feel native