From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
James Linder <james.h.linder@gmail.com>,
git@vger.kernel.org
Subject: Re: NYU Open Source Programming Class Releases JavaGit API 0.1.0 Alpha
Date: Tue, 5 Aug 2008 03:10:51 +0200 [thread overview]
Message-ID: <20080805011051.GC32184@machine.or.cz> (raw)
In-Reply-To: <alpine.DEB.1.00.0808050127510.9611@pacific.mpi-cbg.de.mpi-cbg.de>
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
next prev parent reply other threads:[~2008-08-05 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 16:48 NYU Open Source Programming Class Releases JavaGit API 0.1.0 Alpha James Linder
2008-08-04 17:54 ` Shawn O. Pearce
2008-08-04 23:36 ` Johannes Schindelin
2008-08-05 0:03 ` A Large Angry SCM
2008-08-05 1:10 ` Petr Baudis [this message]
2008-08-05 1:20 ` Shawn O. Pearce
2008-08-05 1:32 ` Pieter de Bie
2008-08-05 1:46 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080805011051.GC32184@machine.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=james.h.linder@gmail.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).