On Tue, Aug 05, 2008 at 01:36:15AM +0200, Johannes Schindelin wrote: > And I absolutely share the puzzlement of Shawn why anybody would try to do > their own thing in Java, instead of contributing to jgit. > > Especially the fact that "JavaGit" seems to repeat the all-to-obvious > error of Eclipse: to make a platform-independent library that depends on > platform dependent components. [Totally naive question coming with no knowledge of actual size of current JGit's feature set:] Wouldn't it make sense to have an ability to fall back on Git calls for functionality that is not implemented natively yet? If you then don't have Git available, you just don't get the functionality. What's the catch? It seems to me that JavaGit's goal is "features, quick!" where JGit's goal is "functionality, thoroughly". Both goals seem legitimate to me, but I'm also not sure why didn't JavaGit just extend JGit's missing bits with native Git calls and instead opted for reimplementation from the ground up. -- Petr "Pasky" Baudis The next generation of interesting software will be done on the Macintosh, not the IBM PC. -- Bill Gates -- 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
