My vote most certainly goes for "ruby/epic" and for many reasons...
Quite a few of my reasons for wanting ruby/epic over epic5 have already been
mentioned in other posts so I will be as brief as possible.
First, I would like to mention that I have spent many years working with the
ircII scripting language (under EPIC and BX) and have become quite adept at
using it. I feel that this should give more weight to my opinion that ruby/epic
is the way to go.
Like a lot of you, I would have quite a bit to rewrite and quite a bit to learn
if we were to make the transition to ruby/epic. Even so, the possibility of
ditching the mess known as ircII and being able to customize my client with
a real scripting language (or some terrible language of my choice! *grin*)
sounds all too good to me.
Also, as many have mentioned, I feel that as far as ircII clients go, EPIC4
does the job quite nicely and although there is still quite a bit that can
be improved, I feel it would almost be wasted effort to continue trying to
_fix_ the existing mess. I find it far more appealing to let Jeremy use the
knowledge he has gained in writing EPIC up until now to create something new
from the ground up. There is almost unlimited potential in such a client.
In summary, I think EPIC4 is plenty to hold us over until Jeremy can give us
a usable ruby/epic client.
PS. Although I'm pushing the whole ruby/epic thing very hard, I will support
whole-heartedly whatever final decision Jeremy (and the rest of you) decide.
--
Brian Weiss <[EMAIL PROTECTED]>
http://we.got.net/~brian/
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
