If the author doesn’t specifically make a declaration in the readme, is there a way to guess how “vibe coded” a project is?
Like I want to know if there is anyone actually in charge… A human who knows at least how to program their own program.
If the author doesn’t specifically make a declaration in the readme, is there a way to guess how “vibe coded” a project is?
Like I want to know if there is anyone actually in charge… A human who knows at least how to program their own program.
it makes me suspicious when it’s fast, but since before vibecoding, i would come across projects that were uploaded all at once, updated quickly and then often never again.
i always thought it was probably people uploading their school projects or something.
usually for those the commit would be something like “upload files”
I’m definitely one of those “upload everything at once” people (I hate git and will not put up with it until it’s needed to actually collaborate on things), but a vibe coded project’s commit history is going to be different. An “upload all at once” person will have a commit that’s like “initial commit” and then a few small patches fixing errors. A vibecoder will have an initial commit then several huge patches, often multiple per day, as they actually do it.
It’d be easy for a vibecoder to fake the “upload all at once” flow by scrubbing the git history and just putting it online as a single initial commit, but their tools default to using git, and they’re lazy.
Damn, I legitimately can’t not use it. It lets me basically set a restore point then go ham on some dumb idea and just create a branch if there are things I like and revisit it later.
How do you manage larger personal projects without that superpower lol.
Perforce.
Isn’t that just git with bloat though? You can use git from the command line or in your ide without ever touching the hub.
Hell, half the time my remotes are just another computer on my network.
What? No, perforce is a completely different version control system with a completely different CLI than git.
I haven’t used it, but the descriptions were talking about managing git repos. Is it like a fork of SVN or Fossil or something?
I can understand the marketing material being vague about the backing and just using the word “git repo” for a vc system.
Edit: I looked into it more and it seems like it’s specifically designed for multimedia version control at a large scale. Seems interesting, definitely has more in common with SVN than Git due to the central server architecture.
Still weird that Wikipedia and even some of their marketing material uses the term “git repo” so often when it isn’t git. Even if it can support git repos on the server.
No, Perforce has been around for ages, it’s older than git, svn, and fossil.
It’s unpopular because it’s owned by one proprietary company that doesn’t really know how to compete with the free-and-everywhere git.
I would much prefer a FOSS clone of perforce over the proprietary thing, but I find its command line interface so much better than git that I use it anyway.
I’ll have to look into it now, had never heard of it, but it seems to be pretty widely used in the industry.
I assume someone who really wanted to fool me probably could, because I’m not very sophisticated. I’m just looking to discern the simple stuff.