Re:Let's Make Sure GitHub Doesn't Become the Only Option
by Sander_Marechal on Tuesday May 02, 2023 @10:27AM
(#35787970)
Yes, MS Visual Sourcesafe (VSS). It was... not very good
[ Parent
| on HN ]
Re:Let's Make Sure GitHub Doesn't Become the Only Option
by grimjack00 on Tuesday May 02, 2023 @10:36AM
(#35788130)
It was, however, a step up from the shared network drive with a bunch of zip files.
Re:Let's Make Sure GitHub Doesn't Become the Only Option
by politician on Tuesday May 02, 2023 @10:47AM
(#35788296)
Debatable. You would come into work in the morning and find that VSS had been corrupted and needed to be restored to an earlier backup. This was a common occurrence.
Re:Let's Make Sure GitHub Doesn't Become the Only Option
by prepend on Tuesday May 02, 2023 @11:12AM
(#35788745)
That the lovely common occurrence of someone checking out 1000 files and going on vacation.
I preferred just a normal folder, rsync (or some nt utils equivalent) and backups.
Re:Let's Make Sure GitHub Doesn't Become the Only Option
by wheelie_boy on Tuesday May 02, 2023 @10:44AM
(#35788267)
they also had an internal source control system that they never released, which was a fork of perforce that they had purchased the rights to use and modify. Not sure if that's still in use in any projects.
Re:Let's Make Sure GitHub Doesn't Become the Only Option
by AndrewStephens on Tuesday May 02, 2023 @11:02AM
(#35788558)
Back in the late 90s we used to call it Visual SourceSieve - code changes would just leak away through the holes. Words cannot explain how much of a step up git (or even SVN) was.
As I recall, the main problem was that VSS didn't have a proper server! Instead the client modified files in the repository directly using Window's file sharing, relying on locks to maintain consistency. This would have been a bad idea even in Window's file shares weren't slow and buggy.