On 3/30/07, Jeremy Henty <jeremy / chaos.org.uk> wrote:
> On 2007-03-30, S. Robert James <srobertjames / gmail.com> wrote:
>
> > I've used http-access2, soap4r, REXML, popen4, rubygems, etc., and
> > the Ruby interpreter itself, and eventually hit bugs in every single
> > one of these, at least on some platforms.
>
> I've used Oracle and hit bugs.  I guess that proves that Oracle isn't
> enterprise ready.  (OK, it was Oracle 8, but still...)

I don't think these are concerns that Robert has.  They're concerns
that the enterprise community as a whole has, he's just essentially
relaying them to us.

We're not discussing the legitimacy of these concerns.  For the most
part we believe they're just ill-conceived.  But the fact is that they
exist, and because they exist we can't explain them away with plenty
of reason.

Simply put, we can't address those concerns directly.  We must ask why
those concerns exist, whether we want to eliminate them, and why, if
not, we don't want to.

Ultimately does this come down to a question of developing culture.
Is the current Ruby culture willing to accept an enterprise culture in
the future?  Are we threatened by them?  Are we going to let them in
but still treat them as outsiders?  Should we try to exclude them
completely?

Bottom line is that curiosity will win over flimsy reasons every
time...so unless you have a damn good reason as to why we should
exclude the enterprise, they're going to make their way into our
culture.  We should do what we can to make them comfortable, and
hopefully guide them to a better way but understand when we can't.  If
we're afraid that our culture will be ruined by a tiny drop of poison,
we don't have a culture strong enough worth protecting.