Login
You're viewing the f.duriansoftware.com public feed.
  • Oct 15, 2026, 3:19 AM

    @mcc but yeah I would never ever go back to CVS, I used it professionally for years and that's a thing best left buried

    but also when I started my career, CVS was still "too new" and a lot of places still used RCS over nfs, and gosh *that* was a mess.

    💬 1🔄 1⭐ 2

Replies

  • Oct 15, 2026, 3:37 AM

    @fluffy @mcc

    HP’s bespoke in-house version control was the first time I saw CGI in action — they’d just spun up a web interface for it — and I realized that web servers didn’t have to just respond to a request by reading a file from the disk, and it blew my mind.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 3:44 AM

    @mcc @fluffy

    It was purely in-house, made at HP and only used there. Can’t remember the name. It did suck, but it was arguably better than CVS!

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 5:23 AM

    @mcc @fluffy

    Which post? If I see the list, it might jog my 30-year-old memories. Would have been used in the developer tools group. Hmmm, did it maybe go by “SCM?” Or am I thinking of something else?

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1
  • Oct 15, 2026, 4:14 AM

    @aizuchi @mcc At my first job out of college we used RCS over NFS even though CVS existed by then, because the CTO of the company was Very Smart and had a belief that CVS was troublesome because he didn't want to learn how to resolve conflicts.

    The repository also used strict locking and pretty much all of the functionality was in one gigantic .c file that people would always forget to checkin/unlock before going on vacation.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 15, 2026, 4:17 AM

    @aizuchi @mcc of course perforce also has the same problem and that's what every place I worked used before git took over.

    (It's less of a problem if you actually use branches in perforce but I can count the number of places I worked at that used perforce with branches on a single finger.)

    💬 0🔄 0⭐ 0
  • Oct 15, 2026, 4:29 AM

    @fluffy @aizuchi so the thing is you want locking on binary files but on source files you want merges. Plastic got this right.

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 4:30 AM

    @mcc @aizuchi Agreed yeah

    git-lfs kinda-sorta works around the binary file locking issue well enough at least, but in such a weirdly roundabout way.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0