On 9/1/06, Rob Sanheim <rsanheim / gmail.com> wrote:
> I find it amusing that he says Rails is too risky and new, yadda
> yadda, but then he goes on to talk about their in-house language,
> "Wasabi":

> So Rails is too risky, but inventing your own language isn't?  Did
> someone say "not invented here" ??

Yes, *Joel* did. He makes quite a strong case for it:
"in defense of not-invented-here syndrome"
http://www.joelonsoftware.com/articles/fog0000000007.html

> Also, I could see how looking at unicode in Rails could scare large
> enterprise apps, but the scaling and slowness thing is just FUD.

The unicode issue is scary to an enterprise mindset, where having
a valid unicode mechanism that is 'non-unicode centric' still qualifies
as 'unicode antipathy'. The enterprise mindset has become happy
with the fact that unicode support is one of those things that they
don't have to think about in the languages/frameworks they favour.

The scaling/slowness thing though I can kind of understand (the
concern that is). I get
the feeling that Rails performs properly when you stick to the promoted
model, but if you deviate from it (processing too much, rather than
using the stack properly) you can choke your performance. Other
languages are probably more forgiving in this respect.

Don't forget the original context of Joels post: "Which web technology
would you bet your company on" (and by implication you house &
savings and whatever other assets you have used to get capital)