Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I hear you, but I don't think git alone (a single repository, at least) provides what is needed for the ideal workflow. Would you agree there are drawbacks to committing by default compared to a sandbox?

Version control in Plandex is like 4 commands. It’s objectively far simpler than using git directly, providing you the few operations you need without all the baggage. It wouldn't be a win for me to add new commands if only git was necessary, because then the user experience would be worse, but I truly think there's a lot of extra value for the developer in a sandbox layer with a very simple interface.

I should also mention that Plandex also integrates with the project's git repo just like aider does, so you can turn on auto-apply for effectively the same exact functionality if that's what you prefer. Just check out a new branch in git, start the Plandex REPL in a project directory with `plandex`, and run `\set-config auto-apply true`. But if you want additional safety, the sandbox is there for you to use.



The problem is I'm too comfortable with git, so I don't see the drawbacks to committing by default. I'm open to hearing about the shortcomings and how I'd address them, though that may not be reasonable to expect for your users.

The problem isn't the four Plandex version control commands or how hard they are to understand in isolation, it's that users now have to adjust their mental model of the system and bolt that onto the side of their limited understanding of git because there's now a plandex branch and there's a git branch and which one was I on and oh god how do they work together?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: