Skip to main content

Do I need to switch to Git from SVN

In recent years GIT has had great momentum it is increasing its popularity. More and more teams are switching to GIT from SVN. This fact raises the question of should I switch to Git from SVN.

To answer this question I made internet investigation relying on poplar search engines. I looked at the user reviews, considered their arguments. Then I started to use Git in parallel with SVN. 

Here comes my experience with both of them.

Both of them are great version control systems. Most apparent difference is that Git is decentralized which means you do not have to use a single repository at the center.  

I found SVN is better in simplicity. Every body easily starts using SVN. It is workflow is quiet simple: update, modify, commit. Revision number logic in SVN is great to have. I use version number to name jar files, This way I can easily follow which jar corresponds to which version. 

I found Git is better for not needing constant connection to central repository. I can frequently commit changes without needing a connection. I can even use Git in my personal project without any remote repositories. I create bare repository in a local folder and use it as a central repository. I found that Git is better for branch tasks. 

Those are result of my hands on experiences after using them together for 2 years. My final word is that do not switch to anything after a complete investigation about pros, cons and the degree it satisfies your needs.

Other than those listed you may see many arguments about the topic some of which are not correct or up to date. For an extended discussion you may have a look at the link below. 


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Obfuscating Spring Boot Projects Using Maven Proguard Plugin

Introduction Obfuscation is the act of reorganizing bytecode such that it becomes hard to decompile. Many developers rely on obfuscation to save their sensitive code from undesired eyes. Publishing jars without obfuscation may hinder competitiveness because rivals may take advantage of easily decompilable nature of java binaries. Objective Spring Boot applications make use of public interfaces, annotations which makes applications harder to obfuscate. Additionally, maven Spring Boot plugin creates a fat jar which contains all dependent jars. It is not viable to obfuscate the whole fat jar. Thus obfuscating Spring Boot applications is different than obfuscating regular java applications and requires a suitable strategy. Audience Those who use Spring Boot and Maven and wish to obfuscate their application using Proguard are the target audience for this article. Sample Application As the sample application, I will use elastic search synch application from my G...
4 comments
Read more

Hadoop Installation Document - Standalone Mode

This document shows my experience on following apache document titled “Hadoop:Setting up a Single Node Cluster”[1] which is for Hadoop version 3.0.0-Alpha2 [2]. A. Prepare the guest environment Install VirtualBox. Create a virtual 64 bit Linux machine. Name it “ubuntul_hadoop_master”. Give it 500MB memory. Create a VMDK disc which is dynamically allocated up to 30GB. In network settings in first tab you should see Adapter 1 enabled and attached to “NAT”. In second table enable adapter 2 and attach to “Host Only Adaptor”. First adapter is required for internet connection. Second one is required for letting outside connect to a guest service. In storage settings, attach a Linux iso file to IDE channel. Use any distribution you like. Because of small installation size, I choose minimal Ubuntu iso [1]. In package selection menu, I only left standard packages selected.  Login to system.  Setup JDK. $ sudo apt-get install openjdk-8-jdk Install ssh and pdsh, if...
3 comments
Read more

Java Thread States

Java Threads may have 6 states: new , runnable , terminated , blocked , waiting , timed_waiting . When a thread is created it is in new state. When start method of thread is called it enters runnable state. Runnable state has two inner states: ready and running . If thread is eligible for execution it is said to be ready, if it is executing it is in running state. Remember calling start method on a already started thread will raise IllegalThreadStateException. When thread finishes its execution it enters into terminated state. When a thread is trying to access a resource, a synchronized statement for example, and it is not available, lock of the object is already acquired for example, it is blocked and said to be in blocked state. When lock is released an thread has chance to acquire lock it goes back to runnable state. When a thread calls join or wait method it enters into waiting state. When joined thread finishes or for wait method notify/notifyAll metho...
1 comment
Read more