What I dont like is that it makes all code visible to the general public. That is what I also don't like about google source version control, hence why I don't use it. Lets say you are making something proprietary and you discover a new paradigm or design pattern, then bam.
What I dont like is that it makes all code visible to the general public. That is what I also don't like about google source version control, hence why I don't use it. Lets say you are making something proprietary and you discover a new paradigm or design pattern, then bam.
Version control doesn't make code visible to the general public... And "google source version control" what is that ?? All google provides is a free hosting service for third party source control (read: git, hg, svn...) and asks only that you make your source open. If you want it to be private then you need to go else where and pay for the service (there are other free feature-deprived, ie no bug tracking, private solutions such as bitbucket).
hence, I don't use it. I use tsvn for my purposes.
For some reason I still feel you don't know the difference. Saying you use tsvn when discussing web hosting... tsvn is still just svn but with a GUI interface instead of typing on the command line. The server hosting your svn repo will use the same server service as svn regardless if you are using tsvn or not.
Git is a necessity in my eyes. It's especially handy on group or large scale projects.
I use it with a SourceForge repo. Recently had to do a group project where no version control was available. It is in its absence that you realise how important and useful it is.