hehe because I'm not doing the client side stuff. Jifty is in my opinion, just as compelling as Rails for what i want it for. But I'm not working alone on this project, and as you must know, we've lost a web sized generation of programmers to python, php and now ruby. Thus, the same way I trust perl, lots of people trust other languages. So please don't think that it is _I_ who feels this way. I could go it alone, but I don't know the web code for 'turquoise' ;)
On 2/19/07, Jesse Vincent <[EMAIL PROTECTED]> wrote:
On Mon, Feb 19, 2007 at 04:17:56PM -0500, Chorg Heavy Industries wrote: > Alas .. it's out of my hands now. I don't have an idea of a design centric > UI toolkit. What I do know is that perl is a very hard sell to people who > know the web code for 'turquoise' ( apparently that color is blue (??) ) > Mason was rejected.. so now I think I'll have to go to my fallback position > ( Ruby/Rails ) to avoid the foul PHP coding. I'd rather die for Enron then > live for PHP again. Ok. So, Why was Rails templating system ok when mason wasn't? (Not starting an argument. Trying to learn) _______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
-- ---------------------------- As folk wisdom says: a clever person is one that gets out of a trap that a wise one would not have got into in the first place.
_______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
