Regarding "Call for help"

[Olaf Faaland]

Perhaps this keeps coming up because those suggesting the re-write don't have 
an idea of how much effort would be required.  How about adding something 
like this to the FAQ?

"As of this writing, GnuCash includes xxx,xxx source lines of code.  
Re-writing that body of code in your favorite language would require at least 
yyy person-months of coding (zzzz years if done by the current developers).  
It's not at all clear that changing languages would make the application 
easier to maintain, attract any more developers than currently exist, or make 
adding features any easier.  Adding features and fixing bugs, on the other 
hand, will clearly contribute to the long-term health of the application and 
the project as a whole by attracting users and developers."

Or, if you think this is too long-winded, just slip in an estimate of the 
effort somewhere.

On Sunday 17 August 2003 04:22 pm, Chris Lyttle wrote:
> Perhaps you could just read the following FAQ in the GnuCash Wiki;
>
> http://gnomesupport.org/wiki/index.php/Frequently%20Asked%20Questions%20%28
>FAQ%29
>
> Chris
>
> On Sun, 2003-08-17 at 15:23, Daniel Carrera wrote:
> > On Sun, Aug 17, 2003 at 06:18:53PM -0400, Derek Atkins wrote:
> > > Daniel Carrera <dcarrera at math.umd.edu> writes:
> > > > Well, the idea was to attract developers who would not be willing to
> > > > tackle Scheme but might be willing to use something else.
> > >
> > > If you know python or ruby or perl then you can learn scheme.
> > > Not being _willing_ to learn scheme is a different issue, and
> > > has nothing to do with simplicity.
> >
> > Alright, if you say so.  I don't know scheme.  I realize I'm speaking
> > from a point of view of ignorance.  I was under the impression that
> > scheme was very difficult to learn and use and I thought that changing
> > that might lower the barrier for colaborating with GnuCash.
> >
> > > It's more trouble than it's worth -- maintaining the scheme bindings
> > > are hard enough.
> >
> > Alright.  Thank you for responding to my suggestion.