Re: [Axiom-developer] BAD tim

2005-11-03 Thread root
> Hello everybody, Hey, Scott! > > This is my first posting to this list. I worked at IBM Research off and on > for 9 years. I'm the primary author/designer of the interpreter and > HyperDoc, and I wrote the first code generator and optimizer for Aldor > (then called A#). > > I found Tim's po

Re: [Axiom-developer] BAD tim

2005-11-03 Thread Scott Morrison
Hello everybody, This is my first posting to this list.  I worked at IBM Research off and on for 9 years.  I'm the primary author/designer of the interpreter and HyperDoc, and I wrote the first code generator and optimizer for Aldor (then called A#). I found Tim's posting very interesting, and I

Re: [Axiom-developer] BAD tim

2005-11-02 Thread Martin Rubey
Dear Tim, Bertfried, * Bertfried Fauser <[EMAIL PROTECTED]> writes: > Dear Tim, > > thank you for your long mail and the invitation to a coofee which > I took while reading... I'd like to second that, although I did not have coffee available. (should go on Axiom's wishlist, I suppose) >

Re: [Axiom-developer] BAD tim

2005-11-01 Thread C Y
--- Camm Maguire <[EMAIL PROTECTED]> wrote: > "Future-proofing", IMHO, is a continous process by any living > project. It requires an active developer base intimately familiar > with the system details which can only be acquired gradually through > time. Developing this base is the key issue IMH

Re: [Axiom-developer] BAD tim

2005-11-01 Thread Camm Maguire
Greetings! "Bill Page" <[EMAIL PROTECTED]> writes: > Tim, > > > POINT 1: Axiom needs to be future-proofed. > > > >Axiom needs to be torn down, re-architected, re-thought > >and rewritten cleanly so it can be modularized, maintained, > >and extended. Which implies a major rewrite, li

Re: [Axiom-developer] BAD tim

2005-11-01 Thread Bob McElrath
I've said it before, but... This whole argument can be broken down into: who is coding, and what does he want? The answer is Tim, and he's going to get what he wants by default. ...Unless one of the rest of us is willing/able to pony up the level of work that Tim is doing, then it makes sense fo

Re: [Axiom-developer] BAD tim

2005-11-01 Thread Bertfried Fauser
Dear Tim, thank you for your long mail and the invitation to a coofee which I took while reading... Perhaps I may add, that as a _user_ of AXIOM, I am totally ignorant to its internal struggles (bild process from scratch, historical accidents, etc), but that I need to focus my resources.

Re: [Axiom-developer] BAD tim

2005-10-31 Thread Vladimir Bondarenko
Hello all, ThD> (so the hero has time to sneak around behind me and kill me) :-) My heart is set strongly against this ;) Viva la Tim! ;-) Vladimir Bondarenko http://www.cybertester.com/ http://maple.bug-list.org/ http://www.CAS-testing.org/ ___

RE: [Axiom-developer] BAD tim

2005-10-31 Thread Bill Page
Tim, Thanks very much for the good humour and detailed reply. On October 31, 2005 10:00 PM you wrote: > > Ah, language wars ... the only thing that out-emotions a > license war Damn! And I just finished saying I didn't want to start such a war... > > I suppose, having been cast as the bad guy