News for hackers. Stuff that matters.
Re:GitHub Sunsetting Subversion Support by rr808 on Friday January 20, 2023 @02:19PM (#34458300)
How about Visual SourceSafe? I actually loved that for a small team.
Re:GitHub Sunsetting Subversion Support by masklinn on Friday January 20, 2023 @02:37PM (#34458560)
> I actually loved that for a small team.

That's a joke right?

VSS is by far the shittiest VCS I've had the displeasure to use, though I will confess I never had to suffer through RCS and CVS.

It's certainly the only one which managed to destroy data. 'twas a good thing I'd already used other source control systems before VSS, because that experience would definitely have made me flee from source control systems for a while (much as Java did static type systems).

Re:GitHub Sunsetting Subversion Support by arcticgeek on Friday January 20, 2023 @04:46PM (#34460410)
We used to call it Visual Source Shredder because of how easy it was to corrupt the database.
Re:GitHub Sunsetting Subversion Support by tialaramex on Friday January 20, 2023 @02:27PM (#34458418)
Are you serious? I'm not even sure if Visual SourceSafe is better than "Once a week I copy all the files into a ZIP and date it" as a strategy for version management.
Re:GitHub Sunsetting Subversion Support by msbarnett on Friday January 20, 2023 @03:36PM (#34459537)
for one thing, zips are far less likely to destroy data than sourcesafe, which was famous for doing just that
Re:GitHub Sunsetting Subversion Support by ianmcgowan on Friday January 20, 2023 @02:49PM (#34458775)
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 by TimTheTinker on Friday January 20, 2023 @02:59PM (#34458927)
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.

Re:GitHub Sunsetting Subversion Support by rr808 on Friday January 20, 2023 @03:55PM (#34459810)
Lol the comments. I went through Perforce and ClearCase too.
Re:GitHub Sunsetting Subversion Support by msoucy on Friday January 20, 2023 @04:34PM (#34460264)
I try to forget ClearCase.

It haunts my nightmares.

When we were migrating to git, some of the more senior engineers came up with a workflow that was described as "the best implementation of ClearCase in git that I've ever seen". It was meant as a compliment.

Re:GitHub Sunsetting Subversion Support by pianoben on Friday January 20, 2023 @03:05PM (#34459029)
We used it at my first job, up until a disgruntled contractor locked every single file in our repo on the day he got fired. We couldn't do a damn thing for like a week, until we migrated to... TFS, sadly, but even that was an improvement.
Re:GitHub Sunsetting Subversion Support by sakopov on Friday January 20, 2023 @07:21PM (#34462234)
I remembering checking in PDF templates into that thing and then never being able to open them ever again because VSS just randomly corrupted files.