I disagree with Git having a steep learning curve. As more practice is put into learning how to use it on a daily basis, it becomes more and more natural to use it, even the most “abstract” concepts.
Using the command line is the basic of the basics for a developer. It is perhaps the “starting point”, so it should be one of the main things to invest first and then become as natural to use it for all things Git. Nevertheless, GitHub has a great tool called GitHub Desktop. I have used it a couple of times in the past and had a great experience. It makes Git less “abstract” to someone getting started.
As for security, Git has an absolutely great approach to security, from cryptographic hashing to checksums to verify the data integrity, access control mechanisms (user authentication and authorisation, for example) and secure transport protocols (HTTPS and SSH, for example).
Subversion and CVS have one particular command that can be misleading: checkout. Git is much more explicit in this with git clone. checkout has a different purpose in Git and Subversion & CVS - to change to a different branch, which is why Git’s clone makes way more sense, in my opinion.
Learning git is not really difficult but it is relative to the others but it is more flexible, secure, fast, and basically an industry standard. Thanks for the engagement
Declined computer engineering as first offer. had fun as webmaster. got my feet wet again as the tech partner went MIA. If you are thrilled on fun projects, burning to grow together as team
I think what the author meant is git requires more on command line. It is true that command line is a basic for all developers. I faced a challenge that I need to showcase stuff to non-technical clients or crews. Or sometimes non-technical team members need to access or edit.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I disagree with Git having a steep learning curve. As more practice is put into learning how to use it on a daily basis, it becomes more and more natural to use it, even the most “abstract” concepts.
Using the command line is the basic of the basics for a developer. It is perhaps the “starting point”, so it should be one of the main things to invest first and then become as natural to use it for all things Git. Nevertheless, GitHub has a great tool called GitHub Desktop. I have used it a couple of times in the past and had a great experience. It makes Git less “abstract” to someone getting started.
As for security, Git has an absolutely great approach to security, from cryptographic hashing to checksums to verify the data integrity, access control mechanisms (user authentication and authorisation, for example) and secure transport protocols (HTTPS and SSH, for example).
Subversion and CVS have one particular command that can be misleading:
checkout. Git is much more explicit in this withgit clone.checkouthas a different purpose in Git and Subversion & CVS - to change to a different branch, which is why Git’sclonemakes way more sense, in my opinion.All in all, I think Git is still the best option.
Learning git is not really difficult but it is relative to the others but it is more flexible, secure, fast, and basically an industry standard. Thanks for the engagement
I think what the author meant is git requires more on command line. It is true that command line is a basic for all developers. I faced a challenge that I need to showcase stuff to non-technical clients or crews. Or sometimes non-technical team members need to access or edit.