I have some serious gripes with this post. Maybe I've become stuck in my ways, but I really feel that a lot of these ideas are really removing a lot of the flexibility of git.
While there’s (usually small) point in using it just for yourself
I'm sorry, but this statement is just so wrong to me. Using git for small personal projects does not provide just a 'small' advantage. It provides a huge advantage, even just simply being able to revert some work you've done is absolutely necessary in the workflow for someone who is used to using a VCS.
we should remove any manual branch syncing stuff. Our Git client will always stay online, and will always sync local branches state with remotes. When you create a branch, it gets immediately pushed and visible for all other clients connected to the same repository.
???? What. What will this do with multiple remotes, etc?
from now on, you'll just commit locally and, magically, everybody else will be able to see your changes.
This is definitely something I would not want!
As you're working in your branch, you can still reorganise, restructure, reorder and rename commits in your branch. These changes will be incrementally synced to all other peoples’ machines as you go. They'll initially see your mess, but then they'll see all the changes you're doing to make your branch look pretty.
So how do they know when my branch has become public and they can base their work off of it?
Make it web app in order to make it accessible from remote machines via browser
This is not something that should be part of the git core.
A lot of these points need much more thought put into them.
27
u/Evan-Purkhiser Jun 20 '14
I have some serious gripes with this post. Maybe I've become stuck in my ways, but I really feel that a lot of these ideas are really removing a lot of the flexibility of git.
I'm sorry, but this statement is just so wrong to me. Using git for small personal projects does not provide just a 'small' advantage. It provides a huge advantage, even just simply being able to revert some work you've done is absolutely necessary in the workflow for someone who is used to using a VCS.
???? What. What will this do with multiple remotes, etc?
This is definitely something I would not want!
So how do they know when my branch has become public and they can base their work off of it?
This is not something that should be part of the git core.
A lot of these points need much more thought put into them.