Live data from Hacker News

Why Subversion does not suck

blog.assembla.com

1–10 of 40 posts

Why Subversion does not suck

#1
The Subversion Sucks meme is popular on the Internet. However, if we imagine a world without Subversion and other centralized version control systems, it's easy to see why Subversion does not suck, is not fading away, and in fact, has a rapidly growing user base.

Why Subversion does not suck
blog.assembla.com

Re: Why Subversion does not suck

#2
In a world without Subversion, Subversion would be built out of Git. In a world without Git, Monotone, Darcs etc. ... well that's where we were 5 years ago, and it sucked.

Re: Why Subversion does not suck

#3
post #2

In a world without Subversion, Subversion would be built out of Git. In a world without Git, Monotone, Darcs etc. ... well that's where we were 5 years ago, and it sucked.

Did it really suck? I was using subversion in a team of around 15, 5 years ago, and all in all it worked pretty well. It was rare that there would be any issue or that subversion got in the way.

Maybe git is better... maybe it doesn't matter enough to bother changing. But you have to admit these types of things are more about what is "in fashion" than what is better suited to a particular task.

Things go in big cycles. For a few years centralization is excellent, offers massive benefits, then suddenly distributed is excellent offers massive benefits etc etc As the post hinted, I wouldn't be surprised if 5 years from now git is pronounced as a terrible idea, and the trend setters go back to something more like svn.

Re: Why Subversion does not suck

#4
post #3
post #2

In a world without Subversion, Subversion would be built out of Git. In a world without Git, Monotone, Darcs etc. ... well that's where we were 5 years ago, and it sucked.

Did it really suck? I was using subversion in a team of around 15, 5 years ago, and all in all it worked pretty well. It was rare that there would be any issue or that subversion got in the way. Maybe git is better... maybe it doesn't matter enough to bother changing. But you have to admit these types of things are more about what is "in fashion" than what is better suited to a particular task. Things go in big cycle…

It sucked because we didn't have the possibility of distributed version control, even if we really wanted it.

Some people and some projects prefer centralized. That's fine. But you can't build a distributed version control system out of a centralized one.

Re: Why Subversion does not suck

#5
"Even designers can use it."

Why does everyone assume that designers are stupid luddites who can't wrap their heads around complex systems? UI design is full of nuance and complexity. It's insulting to designers to assume they cannot deal with DVCS.

Re: Why Subversion does not suck

#6

"Even designers can use it." Why does everyone assume that designers are stupid luddites who can't wrap their heads around complex systems? UI design is full of nuance and complexity. It's insulting to designers to assume they cannot deal with DVCS.

The issue isn't that designers are stupid, it's that, since they tend to have a better design sense (the good ones, at least!), they're generally less forgiving of ugly, needlessly hacked-together systems than people who spend most of their time immersed in them.

Designers are often helpful for a reality check. People should listen to them more!

(There is also nothing about DCVSs that necessitates a bad UI, of course.)

Re: Why Subversion does not suck

#7
The author sets up a false dichotomy: Subersion or git. But those are two different models of source control: centralized and distributed. If you want to use centralized source control, the choice is more likely to be cvs or Subversion.

The popular notion isn't that Subversion sucks, but that it's pointless. The claim I hear is that it's a reinvention of cvs, but it doesn't actually improve much. Personally, I had to learn cvs, it's simple enough for my needs, and I see no reason to switch to something that's fundamentally the same thing.

I think most cvs users are in a similar situation as me. We know Subversion is better, but those benefits seem marginal and not worth the effort to switch.

Re: Why Subversion does not suck

#8

"Even designers can use it." Why does everyone assume that designers are stupid luddites who can't wrap their heads around complex systems? UI design is full of nuance and complexity. It's insulting to designers to assume they cannot deal with DVCS.

Amen.

Meanwhile: To claim that SVN is intrinsically easier to understand than DVCS is to be very shortsighted. Subversion is a more mature technology: It's eight years old, and is conceptually based on CVS, which goes back to the eighties. DVCS is all of eleven years old in its eldest incarnation (according to Wikipedia) and the current generation of tools (git, Bazaar, Mercurial) date back only to 2005.

DVCS is a maturing technology. One of the things that happens as a technology matures is that people learn better ways to explain it to new users, build better interfaces, build better infrastructure.

If you don't think that DVCS makes enough sense to non-geeks yet... give it time.

Re: Why Subversion does not suck

#9

"Even designers can use it." Why does everyone assume that designers are stupid luddites who can't wrap their heads around complex systems? UI design is full of nuance and complexity. It's insulting to designers to assume they cannot deal with DVCS.

Because designers, unlike programmers, have much higher standards for tools. They don't jump on a new "ground-breaking" toy every 2 months, just because someone famous had said "this is THE shit - use it".

Whenever someone says "even X can use it" about some technology, it usually means that either X is stupid, or X is very busy and has no time to waste on "yet another Y".

That said, git can be used in a perfectly centralized fashion, just like SVN. (I use it for automatic synchornization of all my files across 3 laptops via central NAS). And there are some cool GUIs popping up.

Re: Why Subversion does not suck

#10

"Even designers can use it." Why does everyone assume that designers are stupid luddites who can't wrap their heads around complex systems? UI design is full of nuance and complexity. It's insulting to designers to assume they cannot deal with DVCS.

Amen. Meanwhile: To claim that SVN is intrinsically easier to understand than DVCS is to be very shortsighted. Subversion is a more mature technology: It's eight years old, and is conceptually based on CVS, which goes back to the eighties. DVCS is all of eleven years old in its eldest incarnation (according to Wikipedia) and the current generation of tools (git, Bazaar, Mercurial) date back only to 2005. DVCS is a ma…

The article isn't really about SVN vs all DCVSs, though, it's specifally about subversion's interface vs. git's.

There's no reason a DCVS can't have a clean, easily usable interface (darcs's is better than git's, for example), but the git developers have focused on features and raw power over usability.

Post reply on HN