gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: GNUmed on Linux Today


From: Sebastian Hilbert
Subject: Re: [Gnumed-devel] Re: GNUmed on Linux Today
Date: Thu, 11 Mar 2010 10:06:17 +0100
User-agent: KMail/1.13.1 (Linux/2.6.31.12-0.1-default; KDE/4.4.1; i686; ; )

Am Donnerstag 11 März 2010 09:23:20 schrieb Gour:
> On Wed, 10 Mar 2010 20:49:37 +0100
> 
> >>>>>> "Karsten" == "Karsten Hilbert" <address@hidden> wrote:
> Karsten> But I'm glad you feel that way :-))
> 
> One half-serious question: if someone would re-wrote major part of
> GNUmed in say Haskell using Qt toolkit in few months, would you jump
> on the (new) train?
> 
I (Sebastian Hilbert) would not. Simply because I can neither read nor write 
Haskell nor do I have experience with QT. I would support any effort to write 
a GUI in QT but I would not commit to learning Haskell and QT at the moment.

My personal view is that this is a worthwhile goal but builds up new barriers 
for me keeping me from contributing. I personally doubt that in the long run 
more coders can be attracted by using Haskell than python. I guess more people 
have QT skills then wx skills. However there is PyQT available for those.

I understand that this is a half serious question. Would you care to elaborate 
on the reason. Would you be the one rewriting major parts and would you lead 
the development for the next few years. Reason why I am asking is because 
during a rewrite no new code gets added and the project comes to a full stop. 
Which is deadly unless you really know what you are doing.

What happens if the rewrite is planned for a year and after 9 months the idea 
is thrown out ? I can imagine the more fruit bearing way would be you 
rewriting major parts of GNUmed, thereby attracting a group of coders around 
you, thereby making GNUmed as it is pointless through innovation.

All views expressed here are my personal opinion only.

Best regards,
Sebastian Hilbert




reply via email to

[Prev in Thread] Current Thread [Next in Thread]