- cross-posted to:
- programming@programming.dev
- cross-posted to:
- programming@programming.dev
You must log in or register to comment.
Why use Git at all then? I thought the one reason why everyone wants to use Git these days are the forges.
Did you read the article? The author shares their perspective.
For me, Git is quite powerful on its own with version control, diffs, branches, merging, etc. Forges just add a UI for some of these things, and add an issue tracker/ discussion/etc. Forges also add a more modem ui for repo access though git does have its own webserver you can use. I use git without a forge for a number of my personal projects that I’m not sharing with others or not yet sharing
Git is quite powerful on its own with version control, diffs, branches, merging, etc.
All version control systems do that, hence my question.
Git was conceived as a bazaar (because of its use for the Linux kernel), but most projects are more like cathedrals. In my opinion, Git is simply over-engineered for most projects. For projects that you don’t want to share with others, even CVS would probably suffice…
deleted by creator
Mercurial is decentralised, there is no single “source of truth”. (Not counting “upstream”, of course.)
deleted by creator
Both Mercurial and Git started around the same time as a replacement for BitKeeper - which also was decentralised.
CVS would probably suffice…
CVS is awful. Even for local use.
Well just speaking for myself, i use git without a forge for personal stuff because i was already familiar with git and it fits my needs. No need to learn another version control system for some basic projects i throw together
I agree, but subversion is awesome!
It sure is! Glad I’m not alone. :-)
Why use Git at all then?
Still need to version control the work. No editor’s undo buffer is a complete history of all changes
To track changes to a project. You know, the thing Git has been made for.
There is a difference between “not using a VCS” and “using Git”.
Ha! No.
distributed, asynchronous collaboration and versioning.
Or do you wanna send zipped up sourcefiles “project_dev_0.9.6.2_developername_featureID.zip” per email to a dozen colleagues who then have to manually merge it into their current WIP?
There is a difference between “not using a VCS” and “using Git”.
Let me make it clear to you then.
Why use Git at all then?
For it’s VCS features.
I thought the one reason why everyone wants to use Git these days are the forges.
You thought wrong. Git is not wanted exclusively for the forges, but also for it’s VCS capabilities.
Which VCS capabilities make Git stand out in comparison to all other DVCSs if you don’t need a web UI?
Personally:
I am used to git. When I don’t need the webUI, I would stick with git because it is already familiar to me.
Makes sense.
Git experience is highly transferrable. Unless you have some specific use case not supported by Git, why wouldn’t you use the one where the knowledge is most likely to carry over between projects/jobs?
I am one of those weirdos who prefer the best tool for a job, not the most popular one. And Git is - for me and my projects with exactly one branch (“trunk”) and three or four other contributors, with me being the BDFL - the worst choice.
