No love for cvs?
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.
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.
I miss mercurial and it’s far more sensical flags and commands…
It’s still here and very much alive in case you were curious.
Me too. It also handled some situations, like divergent lines in the same branch or obsolete changes, much better.
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.
All of javascript is kinda just pretend.
I find you need the whole ecosystem to support immutability to make it work. Every library needs to be based around it. Elixir is about the only modern option that does.
btrfs sub snap -rIsn’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)
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-project28Truly a Sisyphus tale
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 -fcp?💀
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.
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
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>?It’s not the mechanism of branching that I prefer.
It’s the fact that Mercurial tags the commit with the name of the branch that it was committed to which makes it much easier to determine whether a commit is included in your current branch or not.
Also, Mercurial has a powerful revision search feature built in which I love (https://www.mercurial-scm.org/doc/hg.1.html#revisions).
It’s the fact that Mercurial tags the commit with the name of the branch that it was committed to which makes it much easier to determine whether a commit is included in your current branch or not.
Isn’t this trivial in Git too?
git branch --contains COMMIT?I admit that I have been bitten by the fact that commits don’t have a “true home branch”.
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!
CVS is gonna make a comeback! I tell ya!
I do miss the tags of SVN that would replace certain strings on each commit such as the date, a version number, etc.
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.
And worse than all of those options is Visual Sourcesafe.
Fox Pro!
Shrug








