Version Control

That last one is more common than I'd like, a lot more
- $ cp -r src/ src.old
  No sir never seen it in me life, honest to god sir
- Oh I used to do it as a kid

 bash

    
cd ~/repos/work-project27
git checkout dev
git branch new_feature
### code for a few hours, close laptop, go to sleep, next morning
git checkout dev
### code for a few more hours, close laptop go to sleep, next morning
## "oh fuck, I already implemented this in new_feature but differently"
git checkout dev
git diff new_feature
## "oh no. oh no no no. oh fuck. I can't merge any of this upstream and my history is borked."
git clone git@workhub:work/work-project work-project28
cd ~/repos/work-project28

Truly a Sisyphus tale

At university there were some students that want to manage projekts in could storange. That was just stupid but i didn't know it better at that time.
- I'm sick...that's my excuse....
  
  It's quantum stuff, I could do that, or I could not do that...

The last is just a normal git workflow, isn’t it?
- I'm pretty sure it means, they copy and paste the project file and iterate the version number manually.

the last one is just immutability, praised in modern JS / TS, albeit at the repo level
- I "love" how JavaScript has slowly rediscovered every piece of functional programming wisdom that was developed before 1980.
  
  Kind of, though they honestly just do pretend immutability. Object references are still copied everywhere.

Why did you mention git twice?
- While TFS did support Git, I had to deal with the much worse TFVC for a long while, up until Azure DevOps came along.

MyProject - Copy v2.bak new NEW (3)/
- And when it’s release, then you rename it to
  MyProject - Copy v2.bak new NEW (3) FINAL.2-19-24/
  and then at the next standup, we all ponder how we can rename it to
  MyProject - Copy v2.bak new NEW (3) FINAL.2/19/24/
  because the team lead needs m/d/yy names with forward slashes

It’s actually a pretty good idea to have a full system snapshot time to time, where the project can compile successfully, for future Virtual Machine use. It’s usually easier to spin a VM than setting up the whole dev environment from scratch.

As one of the maintainers of Mercurial, I take great offense in this meme. ;)
- It’s definitely up with Git in my opinion. I much prefer the branching in Mercurial.
  It’s certainly very offensive to lump it in the same band as SVN and TFVC.
  
  What could possibly be preferrable to git switch -c <branchname>?
  
  Given that Git and Mercurial were both created around April 2005 to serve the same purpose by very similar people for the same reason... I'd say it's fair!

Git is so ready to understand, that I don't understand how people work without it.
- It's one of those things that's hard to really understand why it's so useful, until you actually use it.

cp $fic $fic.$(date -Iseconds) git commit -a -m "save at $(date -Iseconds)" # edit $fic git commit -a -m "save at $(date -Iseconds)" git push -f
- cp?💀
  
  cp is short for create packup

btrfs sub snap -r
- With properly configured subvolumes, I'll allow it.
- Isn't that just git with more steps and harder to share?
  
  It's equivalent to cp -r, but:
  the copy is read-only
  reuses unchanged files
  easier to share (btrfs sub send)

Couldn't add perforce to the list because someone else was checking it out, I see.

And worse than all of those options is Visual Sourcesafe.
- Fox Pro!
  Shrug

I do miss the tags of SVN that would replace certain strings on each commit such as the date, a version number, etc.

CVS is gonna make a comeback! I tell ya!

I miss mercurial and it's far more sensical flags and commands...
- Me too. It also handled some situations, like divergent lines in the same branch or obsolete changes, much better.
- It's still here and very much alive in case you were curious.
  
  The only reason that we stopped using Mercurial is that Microsoft used Git in Azure DevOps. I still wish that they’d supported Mercurial instead of or as well as Git.
- I really liked Mercurial too. It was much easier to follow branches to find out if a branch included a commit.

No love for cvs?

The last one can easily describe Django. Feels like depending on the code base/your mistakes/people you work with can easily turn a normal project into a project where majority of the files is just migration files.

cp index.php index.php-20250220

Perforce Helix, here I come!

I knew a dude who would burn a cd every week and store it in his house as his version control, his software is still used by hundreds of businesses to this day