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' ;)
<br><br><div><span class="gmail_quote">On 2/19/07, <b class="gmail_sendername">Jesse Vincent</b> <<a href="mailto:jesse@bestpractical.com">jesse@bestpractical.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><br>On Mon, Feb 19, 2007 at 04:17:56PM -0500, Chorg Heavy Industries wrote:<br>> Alas .. it's out of my hands now. I don't have an idea of a design centric<br>> UI toolkit. What I do know is that perl is a very hard sell to people who
<br>> know the web code for 'turquoise' ( apparently that color is blue (??) )<br>> Mason was rejected.. so now I think I'll have to go to my fallback position<br>> ( Ruby/Rails ) to avoid the foul PHP coding. I'd rather die for Enron then
<br>> live for PHP again.<br><br>Ok. So, Why was Rails templating system ok when mason wasn't? (Not<br>starting an argument. Trying to learn)<br>_______________________________________________<br>jifty-devel mailing list
<br><a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br><a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>----------------------------<br>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.