4 ms·
Exactly, that something as trivial and obvious as version control costs so much mental overhead is completely bizarre. Sure, SVN doesn't have as many features
by flohofwoe 7y ago
Exactly, that something as trivial and obvious as version control costs so much mental overhead is completely bizarre.
Sure, SVN doesn't have as many features as git, and merging sucks, but it offers the most important features of version control (recording "who has done what, when", and undoing changes). Teaching SVN usage to a non-techie takes literally a few minutes (especially with an intuitive UI like TortoiseSVN), and it's very hard to break something.
- james_s_tayler 7y agoAnd that's why everyone still uses SVN and git is this obscure minor player that's relatively unheard of.
- flohofwoe 7y agoWhether it's specifically SVN doesn't matter really, the point is that no other version control system in history required so much mental effort to be "learned" like git. And the worst thing is that new people who don't know anything else than git think that this is normal. What's happening under the hood is mostly fine (mostly, because git completely breaks down with large binary files, and solutions like git lfs don't help much with this problem). What's really bad is the git "frontend", that there's no obvious standard workflow, instead there's a thousand ways to do the same thing. That's great if you have a lot of time for tinkering and meddling with the tools layer, but not when you simply need to get shit done. The version control system should essentially 'disappear' and never require attention.
- james_s_tayler 7y agoI started on SVN. Had a stint using TFS. Eventually wound up in git. I vastly prefer git. We had simpler, easier to operate version control tools. Git traded off some of that simplicity for other benefits the community at large seems to value enough to have migrated away from the simpler tools. I'm skeptical the "git is too complicated for newbies" cry is truly a turning point in tech cycle where we see the folly of our ways and begin to decry the current flavor of the month at the new anti-pattern after enough real-world experience has been accumulated to show us the error of our ways. I think it's just "I don't like the way this makes me feel".
- taneq 7y agoThat's why everyone should still use SVN (or even something distributed but friendlier, like hg or bzr) and git should be a minor-but-important player that's used where needed (like for managing the Linux kernel, which is what it's actually for). But of course we've cargo-culted it everywhere, and anyone who objects runs up against the pervasive attitude that there are no bad user interfaces or difficult-to-use software, only stupid people.
- james_s_tayler 7y ago>That's why everyone should still use SVN Ah yes, good old normative claims. The market wants what the market wants.
- mrlala 7y agoGitkraken is easy as pie to use and does everything you are mentioning.. not sure why people are so obsessed with command line stuff for version control. Also anything like visual studio / vscode you have 99% of what you normally do right in the UI. I think it's anal people who like to make things as complicated as possible who try to make git as complicated as possible for others.
- iovrthoughtthis 7y agoWe teach students SVN as a part of software engineering at the Uni where I work. 70% of students screw up their repository every year. My experience is that SVN is just as hard as git for the purposes of managing versions and branches of your work.