future of HgKit
Marcus Dubois
animatify at gmail.com
Sat Oct 3 21:44:28 UTC 2009
>
> I really don't see this as a big difficult problem. The "slave
> daemon" mode is probably the hardest part to get right, since it means
> designing a protocol. But most of the protocol is already there in
> the form of hg's command-line UI; you just have to turn that into
> socket I/O rather than argv and stdout. But the Java side of things
> really should not be much code. There is no need to port or rewrite
> Mercurial in Java.
Well yes I agree with you on that point, but I also think that a second
implementation of Mercurial in another PL wouldn't hurt. For example
take Ruby you have JRuby and Rubinius. Somehow they benefit from
each other and coexist.
Rewriting Mercurial in another PL could be just an exercise in writing
a DVCS but it could also benefit Mercurial as a whole. As for the licenseing
issues I'd stick to GPL v2.
/Marcus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20091003/2fabea3b/attachment-0001.html>
More information about the Mercurial
mailing list