Robin Rosenberg <robin.rosenberg.lists@xxxxxxxxxx> wrote: > > The Eclipse Git plugin closing in on a 0.3 version. This is a good chance for me to say thank you to Robin and Dave Watson for taking over the Eclipse Git plugin and working on it over the past few months. The progress Robin described in this issue of the EGIT Chronicles is due to their hard work. > As mentions, the plugin is pure Java, but I'm pretty sure there > will be features that directly depends on having a native Git > installed. What features will suffer from that depends on who > writes the code. So far we simply depend on having native Git for > operations like clone/push/fetch, merge. blame and everything else > not yet implemented. Complexity and performance are obvious concerns. > > Now re-implementing Git in Java because it is a much better language > is *not* the driving force behind reimplementing core parts of Git > in Java. It is the fact that having multiple languages by itself > causes problems with building and distribution and the complexity > of and performance loss from interfacing with native code must be > compared to the complexity of writing replacement code. The fun > factor must also be taken into account. I program in Java at day-job, and Tcl and C at night on Git. I'm not convinced Java is a better lanaguge. :-) But that said the primary reason why I strived to keep EGIT pure Java when I was actively developing on it was to make it easy to integrate into Java applications. Calling command line executables from Java is not fun, especially if you need to scrape the output to present the information to the user. Trying to link native code into a running JVM tends to be more of a challenge than it should be, and makes the code less portable. -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
