Oh really? Do pray tell, just how is it a ruby framework ?
I don't know if you've ever explored any artistic endeavor unrelated to programming - but I look at it like that. Every day in everything you do in any art / language / whatever you always learn new "good" things and new "bad" things. The artist part comes in when you successfully take your own version of good from all these points and form your own expression being the sum of all that is good. (or crap, depending on how good you are at your art ;) ) Stop trying to pigeon hole everything as being either completely one thing or another. It just is. Try embracing it a little. Maybe start somewhere smaller like contributing some components / documentation / etc. I'm sure Howard has plenty of things in mind he'd like to do if you ask him. On 2/20/07, Kent Tong <[EMAIL PROTECTED]> wrote: <snipped>
But anyway, please don't waste any more time on this issue as it is now clear that Tapestry 5 is going to be a Ruby web framework for Java programmers. As such I fully agree that compile time checking and first class IDE support are conflicting goals. -- Kent Tong Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]