[implementations-list] fork viper?

Jason Spiro jasonspiro3 at gmail.com
Fri Jan 1 22:08:42 CET 2010

On Fri, Jan 1, 2010 at 9:57 AM, John J. Foerch <jjfoerch at earthlink.net> wrote:

> I don't use Viper myself so take this with a grain of salt.. Have you
> considered forking viper, instead of having all these modes that run on
> top of it?  Having many modes that must work in concert with each other
> introduces a level of complexity that was a large part of why I decided
> not to use Viper anymore.

Fair question, and fair point about complexity.

Forking is usually a last resort.  I think it'd be better to get
viper-in-more-modes merged into Viper, and to get all the bugs in
Vimpulse fixed so that Vimpulse can be merged into Viper too.  Then
perhaps the Vimpulse maintainers/committers can get commit rights to
upstream Viper to make it easier to merge future patches.

More information about the implementations-list mailing list