4 ms·

It's funny that the main reason you switched was because of the difficulties of VSS. Your tools forced you to make decisions about how you code! We just switch

It's funny that the main reason you switched was because of the difficulties of VSS. Your tools forced you to make decisions about how you code! We just switched to SVN. The migration was an easy < one day job, a few weeks of pain with some developers grumbling that it was too complex and then everyone was (mostly) happy that we no longer had to hunt down the consultant who had locked a particularly critical file and was now out of the office the rest of the week.

dpark 9y ago
You’ve been on VSS until just recently? That seems insane. Wasn’t the last update to VSS shipped in 2005? Also, why SVN? That seems an antiquated choice at this point.
- eropple 9y ago
  "Just" being "simply", rather than sticking with VSS.
  - dpark 9y ago
    I read that as “recently” rather than “simply”, but could be wrong.
- mattmanser 9y ago
  No, this was a decade ago at a company I used to work for. Although a couple of years ago I did have a job where they used it, but I quit after 2 months. For some reason a couple of the Devs would constantly check in blank commits. Not sure if that was a product of VSS or because the Devs were awful (part of the many reasons I left so quickly). It's not quite as bad any more, but still terrible when compared to Git or SVN.
  - dpark 9y ago
    Ok. That makes more sense. :)
- zimpenfish 9y ago
  One of the first things I did at a contract in 2013 was port their RCS wrapper scripts to SVN. I wept hard for those weeks.
  - dpark 9y ago
    That sounds pretty terrible. Why did they need a bunch of wrappers? I’m a big fan of vanilla tooling. Complex build, version control, etc gets no love and ends up ten years later as a big mess that no one understands or wants to support.
    - zimpenfish 9y ago
      Because their entire workflow had been about these RCS wrappers for 5+ years and they weren't ready to change that for existing projects etc. New projects (such as the one I did after that) were thankfully just plain ol' SVN commands from the start.

dpark 9y ago

You’ve been on VSS until just recently? That seems insane. Wasn’t the last update to VSS shipped in 2005? Also, why SVN? That seems an antiquated choice at this point.

eropple 9y ago
"Just" being "simply", rather than sticking with VSS.
- dpark 9y ago
  I read that as “recently” rather than “simply”, but could be wrong.
mattmanser 9y ago
No, this was a decade ago at a company I used to work for. Although a couple of years ago I did have a job where they used it, but I quit after 2 months. For some reason a couple of the Devs would constantly check in blank commits. Not sure if that was a product of VSS or because the Devs were awful (part of the many reasons I left so quickly). It's not quite as bad any more, but still terrible when compared to Git or SVN.
- dpark 9y ago
  Ok. That makes more sense. :)
zimpenfish 9y ago
One of the first things I did at a contract in 2013 was port their RCS wrapper scripts to SVN. I wept hard for those weeks.
- dpark 9y ago
  That sounds pretty terrible. Why did they need a bunch of wrappers? I’m a big fan of vanilla tooling. Complex build, version control, etc gets no love and ends up ten years later as a big mess that no one understands or wants to support.
  - zimpenfish 9y ago
    Because their entire workflow had been about these RCS wrappers for 5+ years and they weren't ready to change that for existing projects etc. New projects (such as the one I did after that) were thankfully just plain ol' SVN commands from the start.