Because prior to Stable Diffusion coming out I had never even heard of it before and had zero experience using it, and it was frustrating to have to learn an entirely new system as a barrier to entry to learning something else.
>>No other version control system comes even close to git
well it was designed to be extraordinarily powerful and capable of complex manipulations, and to support a distributed community of thousands of developers all working on different bits of things in different ways and different rates.
But there is a case to be made that for simple use cases that don't involve any of that, it's massively complex overkill.
It's overrated. Of course it makes sense when you actually have many contributors, but most of the time I just see people roleplaying on github.
It's just a total waste of time for a solo developer.
>>No other version control system comes even close to git
well it was designed to be extraordinarily powerful and capable of complex manipulations, and to support a distributed community of thousands of developers all working on different bits of things in different ways and different rates.
But there is a case to be made that for simple use cases that don't involve any of that, it's massively complex overkill.
It isn't though, just don't microcommit and you have >Free portfolio you can share around >Free backups for your projects >Free history for when you wanna make experimental changes or break stuff >Overview of your progress and the effort you put in
Just learn it. It can be pretty comfy.
Everyone already knew svn was the better control system, but the gnu/tards on this board will convince u that muh open source technology is the superior one, even though the only people using it are neckbeards and webshitters
most people seem to want SVN basically, but at the same time SVN is too shit to fine grain version shit properly, so I don't know.
git is ok, but I feel like it's overly complex in cases that aren't relevant. also I am a git master so don't @ me about how I don't know how to use it. the problems more come from everyone else not knowing how to use it.
Git is ok but very bloated for simple use cases, unnecessarily complex for slightly less simple use cases, and full of hazards a la filter-branch for complex use cases.
With that said, SVN isn't perfect either, and git is good enough in many practical scenarios.
I taught myself programming and am now working as a data engineer. I use git for all my own projects, but both in my masters program and my job nobody had any idea of what git was or why they should use it. At this rate I doubt I'll ever get some real professional experience working with Git as part of a team
Because prior to Stable Diffusion coming out I had never even heard of it before and had zero experience using it, and it was frustrating to have to learn an entirely new system as a barrier to entry to learning something else.
Yes, see
>>No other version control system comes even close to git
well it was designed to be extraordinarily powerful and capable of complex manipulations, and to support a distributed community of thousands of developers all working on different bits of things in different ways and different rates.
But there is a case to be made that for simple use cases that don't involve any of that, it's massively complex overkill.
It's overrated. Of course it makes sense when you actually have many contributors, but most of the time I just see people roleplaying on github.
It's just a total waste of time for a solo developer.
What should solo devs use?
sex toys
It isn't though, just don't microcommit and you have
>Free portfolio you can share around
>Free backups for your projects
>Free history for when you wanna make experimental changes or break stuff
>Overview of your progress and the effort you put in
Just learn it. It can be pretty comfy.
>just don't microcommit
I hate you naggers
If using git alone causes you to "waste time" then that's some serious skill issue.
Everyone already knew svn was the better control system, but the gnu/tards on this board will convince u that muh open source technology is the superior one, even though the only people using it are neckbeards and webshitters
The UX is obtuse.
most people seem to want SVN basically, but at the same time SVN is too shit to fine grain version shit properly, so I don't know.
git is ok, but I feel like it's overly complex in cases that aren't relevant. also I am a git master so don't @ me about how I don't know how to use it. the problems more come from everyone else not knowing how to use it.
>I am a git master
prove it
>Are people who dislike git just too stupid to use it?
Yes
>No other version control system comes even close to git
Yes
it's the other way around
people who like git are just noobs too stupid and/or inexperienced to realize how retarded git is
Tell us, oh enlightened one. What is wrong with git?
People who dislike Git don't know how to use version control at all.
Git is ok but very bloated for simple use cases, unnecessarily complex for slightly less simple use cases, and full of hazards a la filter-branch for complex use cases.
With that said, SVN isn't perfect either, and git is good enough in many practical scenarios.
how is it bloated?
what are complex use cases you encounter often and can only be fixed with filter branch?
What would you remove from git to improve it?
<code> git init </code>
I taught myself programming and am now working as a data engineer. I use git for all my own projects, but both in my masters program and my job nobody had any idea of what git was or why they should use it. At this rate I doubt I'll ever get some real professional experience working with Git as part of a team