“Developer”
“my” 4 months of “work”Those are the ones easily replaced by AI. 99% of stuff “they” did was done by AI anyway!
Why did the porn star become a network admin after retiring?
She was already an expert in load balancing
svn was invented in 2000
CVS was invented in 1986
Now Target owns them, I think.
SCCS is from 1972, you young whippersnappers
SUN is from 4.6 billion years ago, you mortal beings
I’m a software developer so I’ve never seen that thing you’re talking about, but check your sources, I believe it’s actually from 1982: https://en.wikipedia.org/wiki/Sun_Microsystems
I landed in the middle. SCCS was too old, CVS was too new.
https://www.gnu.org/software/rcs/
But, back then, I had also been forced to use CMVC.
https://en.m.wikipedia.org/wiki/IBM_Configuration_Management_Version_Control
When
bzr, and thengit, turned up and I started using them, I was told “this is DVC, which is a whole new model that takes getting used to”, so I was surprised it seemed normal and straightforward to me.Then I found out that Sun’s Teamware, that I had been using for many years, was a DVC, hence it wasn’t some new model. I’d had a few intervening years on other abominable systems and it was a relief to get back to DVC.
Regarding the original post, are there really people around now who think that before
gitthere was no version control? I’ve never worked without using version control, and I started in the 80s.
git push origin master # moron
The first version control system I ever used was CVS and it was first released in 1986 so it was already old and well established when I first came to use it.
Anyone in these past forty years not using a version control system to keep track of their source code have only themselves to blame.
And Claude, off course.
Before that, it was RCS, released in '82.
Luckily I’m young enough that I never had to use RCS.
Or gnu arch
CVS was, for the longest time, the only player in the FLOSS world. It was bad, but so were commercial offerings, and it was better than RCS.
It’s been completely supplanted by SVN, specifically written to be CVS but not broken, which is about exactly as old as git. If you find yourself using git lfs, you might want to have a look at SVN.
Somewhat ironically RCS is still maintained, last patch a mere 19 months ago to this… CVS repo. Dammit I did say “completely supplanted” already didn’t I. Didn’t consider the sheer pig-headedness of the openbsd devs.
“We’ve always done things this way, we ain’t changing!” - some folks in the Foss community, like those RCS maintainers
which is about exactly as old as git.
Wdym by that?
We still use RCS at work. For config files for our network monitoring. Works fine still.
Pretty sure GTA V use(d) SVN or something like that. I remember reading the source code and being surprised that they didn’t use GIT.
Game developers often use Perforce instead of Git. Maybe it was that?
That’s very possible.
You definitely need something else than git for large assets, yes, its storage layer is just not built for that and they way art pipelines generally work you don’t get merge conflicts anyway because there’s no sane way to merge things so artists take care to not have multiple people work on the same thing at the same time, so a lock+server model is natural. Also, a way to nuke old revisions to keep the size of everything under control.
My first one was Visual Source Safe.
I will never go back to it for any amount of money.
You know, CVS wasn’t really that bad, just primitive and outdated.
deleted by creator
this guy would have force pushed onto main about 10 mins after this if he did have git
And then lost the reflog by
rm -rfing the project and cloning it again.God bless DCVS.
Tbf you have to do that for the first push, if a Readme file was autogenerated
You don’t if you just clone the repo you created.
Huh? I’m talking about existing code being in a dir, then initting a git repo there, creating a pendant on your hoster of choice and then pushing it there. Wouldn’t cloning the repo from step 3 to the code from step 1 overwrite the contents there?
There are multiple solutions to this without using --force.
Move the files, clone, unmove the files, commit, push being the most straightforward that I can summon at this time… but I’ve solved this dozens of times and have never use --force.
If your remote is completely empty and has no commits, you can just push normally. If it has an auto-generated “initial commit” (pretty sure Github does something like that), you could force push, or merge your local branch into the remote branch and push normally. I think cloning the repo and copying the contents of your local repo into it is the worst option: you’ll lose all local commits.
True, in the situation with a local history maybe it’s worthwhile to --force to nuke an empty remote. In that case it is practical to do so. I just typically like to find non-force options.
deleted by creator
Yeah, I was thinking of a new repo with no existing code.
In your case you’d want to uncheck the creation of a readme so the hosted repo is empty and can be pushed to without having to overwrite (force) anything.
Does that still happen if you use the merge unrelated histories option? (Been a minute since I last had to use that option in git)
Never have heard of that, but in the case of you also having a Readme that will be even more complicated, I imagine. So just adding -f is the easier option.
Ahh yes, programming by vibe. The vibe is always dumbass. Just steal code that has already been explained to you like everyone else.
already been explained to you
This step is optional
I just want to pause a moment to wish a “fuck you” to the guy who named an AI model “Cursor” as if that’s a useful name. It’s like they’re expecting accidental google searches to be a major source of recruitment.
It’s not an AI model, it’s an IDE
My comment stands
I need to put a SaaS together called vibe VCS
I remember SVN
I want to forget SVN
I want SVN little explorer icons back! I want to forget Jazz RTC.
It’s a scary amount of projects these days managed by a bunch of ZIP files:
- Program-2.4.zip
- Program-2.4-FIXED.zip
- Program-2.4-FIXED2.zip
- Program-2.4-FIXED-final.zip
- Program-2.4-FIXED-final-REAL.zip
- Program-2.4-FIXED-FINAL-no-seriously.zip
- Program-2.4-FINAL-use-this.zip
- Program-2.4-FINAL-use-this-2.zip
- Program-2.4-working-maybe.zip
- Program-2.4-FINAL-BUGFIX-LAST-ONE.zip
- Program-2.4-FINAL-BUGFIX-LAST-ONE-v2.zip
If we’re talking actual builds then zip files are perfectly fine as long as the revs make chronological sense.
I did that with documents in my Uni years.
By the end, I was using ISO timestamps.- Program-1.5-DeleteThis.zip
- Program-1.6-ScuffedDontUse.zip
- CanWeDeleteThesePlease.txt (last edit 8 months ago)
Inspired by a small collaboration project from a few years ago.
Fake developer doesn’t use version control. Big surprise.
Just save your prompts and vibes in a Google doc dude
Good thing it’s deterministic, oh wait 😃
You could literally just save a copy to your desktop before you’re going to do something sensitive.
Or use VCS like a normal dev
That’s why I take a screenshot of my desktop before something stupid just in case.
It’s actually reassuring to see that despite all warnings and doomsayers there will still be opportunities for programmers capable of solving problems using natural intelligence.
If anything it feels like we’re the doomsayers trying to warn people that their AI bullshit won’t ever work and they’re just not listening as they lay off the masses and push insecure and faulty code.
And then years from now when this all comes to a head, they’re gonna hire some poor schmucks to fix that crappy code
