Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Sunsetting Subversion Support

github.blog

Post reply on HN
Print view View original

41–50 of 238 posts

Re: GitHub Sunsetting Subversion Support

#41

Post by somerando7 »

kypro wrote: post #25

I'd love to hear from someone who's still using SVN professionally and can explain why they prefers it to Git. I used SVN very early in my career. I think the only good thing I can say about it is that it's easier to learn. It's quite easy to teach a junior dev how to use SVN. Git takes much longer to master.

What's better about git? I haven't used svn, but have used perforce/mercurial professionally/git professionally, and use git personally, but I find all of them to provide the same "feature set" when doing basic development: have your own branch, and merge it in to the main branch when done/reviewed.

Merging seems the same on all 3 version control systems I've used... I've heard that git branching is better(?), but haven't seen that being used anywhere really.

Re: GitHub Sunsetting Subversion Support

#42

Post by czx4f4bd »

benatkin wrote: post #35
czx4f4bd wrote: post #22

Earlier quoted context omitted.

> Reminds me of how Microsoft dumped Atom (and then fauxpen-sourced VSCode before dumping the last remnants of Atom). I'm confused by this. Microsoft released the VS Code source in 2015, long before they acquired GitHub in 2018 and sunset Atom in 2022.

They moved Atom into de-facto maintenance mode much earlier than that, when VSCode was much less fauxpen-source than it is now.

Just repeating "fauxpen source" doesn't mean anything to me. What actual change are you referring to?

Re: GitHub Sunsetting Subversion Support

#43

Post by butterandguns »

schacon wrote: post #12

As one of the GitHub cofounders and the brainchild of this particular feature, I want to let everyone know that this is maybe the funniest thing I've ever done. We released this feature and published the announcing blog post, on April Fool's Day, 2010. I remember demoing it to the other GitHub guys and saying how funny it would be if we made this an April Fool's day post as though it was a big stupid joke but then it…

Where did the name slumlord come from?

Re: GitHub Sunsetting Subversion Support

#44

Post by ianmcgowan »

rr808 wrote: post #11

How about Visual SourceSafe? I actually loved that for a small team.

Worst. VCS. Ever! Can't believe anyone ever loved VSS - it was constantly corrupting the repository, people would lock programs and go on vacation, just a constant struggle.

We switched to CVS and it was immediately better, followed by SVN a few years later. I still use git like a fancy subversion, just with multiple repositories :-)

Re: GitHub Sunsetting Subversion Support

#45

Post by mjhay »

adamsb6 wrote: post #37

This reminds me of the time on Something Awful that radium banned the one user that was using WebTV. > About 91% of visitors are on Windows. Mac users make up 5% and Linux is 2%. The other 2% are permabanned IRC trolls browsing the forums with a text-based browser written in Ruby on OpenBSD. Oh yeah, we have one guy using WebTV but I banned him because WTF.

Hadn't heard that one before. Radium's incompetence was really something.

Re: GitHub Sunsetting Subversion Support

#46

Post by gus_massa »

kypro wrote: post #25

I'd love to hear from someone who's still using SVN professionally and can explain why they prefers it to Git. I used SVN very early in my career. I think the only good thing I can say about it is that it's easier to learn. It's quite easy to teach a junior dev how to use SVN. Git takes much longer to master.

One of my friends is using it at work. They have been using SVN since a long time. They have been planning to migrate to Git for a few years. The problem is that customers pay for features, not for the version control you are using. SVN still works, and the inertia is not zero.

Re: GitHub Sunsetting Subversion Support

#47

Post by benatkin »

czx4f4bd wrote: post #42
benatkin wrote: post #35

Earlier quoted context omitted.

They moved Atom into de-facto maintenance mode much earlier than that, when VSCode was much less fauxpen-source than it is now.

Just repeating "fauxpen source" doesn't mean anything to me. What actual change are you referring to?

Big overview: https://ghuntley.com/fracture/

A couple points in time:

Pylance, installed by default, won't open source. Microsoft keeps calling VSCode open source. https://github.com/microsoft/pylance-release/issues/4

Same for .NET https://twitter.com/migueldeicaza/status/1537175065380495367

Re: GitHub Sunsetting Subversion Support

#48

Post by david_allison »

thaeli wrote: post #21

The one thing I really miss about svn is the central,authoritative, auto-incrementing revision numbers. Git hashes are less friendly to use - in the svn days it was easy to tell at a glance if you had an earlier or later version. Yes, I know the many ways that git is better in practice, and would miss some of the workflows git's nature allows if they were gone. But we really did lose something too, especially when ru…

It can be done, but probably shouldn't: https://github.com/zegl/extremely-linear/commits/main

Re: GitHub Sunsetting Subversion Support

#49

Post by kawsper »

CJefferson wrote: post #10

There is only one thing about subversion I miss when using git -- the deletion of branches (which were, admittedly, just directories in a folder called branches) was version controlled, so you could recover deleted branches.

I miss the name, SVN was pronounced Svend (SVeN) among my friends, which is a scandinavian male name.

"Have you committed your changes to Svend yet?", "No, Svend is experiencing some downtime right now", that was some fun interactions that got us through computer science.

Git is a fun name too, but it is not nearly as funny to me.

TortoiseSVN was a great SVN client integrated into Windows File Explorer, and it looked great when you used the classic theme on Windows XP.

Re: GitHub Sunsetting Subversion Support

#50

Post by TimTheTinker »

rr808 wrote: post #11

How about Visual SourceSafe? I actually loved that for a small team.

Jeff Atwood had a lot of negative things to say about Visual SourceSafe back in 2006: https://blog.codinghorror.com/source-control-anything-but-so...

There's some good links there that describe the trouble VSS caused.

Post reply on HN