3 ms·
Can confirm. Git: 50 mins of googling to know what the next 5 commands to type. Hg: 5 mins of googling to know what the next 50 commands to type.
by wyuenho 4y ago
Can confirm.
Git: 50 mins of googling to know what the next 5 commands to type.
Hg: 5 mins of googling to know what the next 50 commands to type.
- hexo 4y agoHg: + another 2hrs of cleaning up disk space so it can "checkout" revision you actually care about
- wyuenho 4y agoIf you need 2 hrs to clean up disk space to checkout a repo, maybe how you organize code is the problem.
- arinlen 4y ago> Git: 50 mins of googling to know what the next 5 commands to type. That's quite the odd statement, as all it takes is a 5min tutorial to get up and running on 95% you ever need to do with git on a weekly basis, and 100% of what you do at an everyday basis. > Hg: 5 mins of googling to know what the next 50 commands to type. This is not the brag you think it is. If you need to know 50 commands to do daily work with a revision control service, that service is appallingly broken by design. Also, you forgot to mention the need to install ad-hoc extensions in mercurial to have access to basic stuff.
- wyuenho 4y ago> That's quite the odd statement It's odd only if you are new to DVCS. In the early days of git and hg, git commands were lots of plumbing and very little porcelain. At the time, most people switching from svn to a DVCS almost universally found hg a basically effortless switch. The success of git is due to 1) Linus fandom/cargo cult. 2) Ruby on Rails groupthink, and 3) Github. > If you need to know 50 commands to do daily work with a revision control service, that service is appallingly broken by design. Commands to type.