M C wrote:
*/Ola Bini <[EMAIL PROTECTED]>/* skrev:
Hi Morten,
You know I don't wholeheartedly agree with this approach. On the
other
hand, it would make sense to package a downloadable JRuby on
Rails-package, which a customized war.rb for Derby use, and things
like
that.
Hi Ola,
Yea, I remember that you don't like me idea when we first talked about
it at RailsConf. However, I hope to be able to persuade you otherwise
which is the reason I wrote a message about it explaining my argument
in details.
I personally think that better integration will help a lot in getting
JRuby adapted and fully recognized for all its great benefits and
possibilities! The current strategy with separate projects only
complicates matters, hides 50% of the most powerful features / real
benefit for users that do not know the JRuby world well.
P.S. Nice talking to you at RailsConf and thanks for arranging a cool
t-shirt for me (even though I am still not sure I fully deserve it as
I have only helped a little so far).
Hehe, of course you deserved it.
And no, I don't necessarily think better integration is a good idea, at
least not if it means bundling stuff that we choose together and making
it more "advanced" to use other solutions. Opinionated software works
fine for Rails, but I don't think it's a good model for a language
implementation. Further, you pay a price for the kind of integration
that MS gives you; namely the lack of choice. The one mainline thing is
very easy to do, but you do it with components decided by MS. As soon as
you stray from the MS path, everything gets much harder. I don't want to
see that happen with JRuby. Which is way I think it would be wrong
making something like goldspike more integrated (there are many who
don't like the way goldspike works at all), it would be wrong to make
assumptions on which database a user wants to use (I mean seriously, a
major selling point for JRuby on Rails is the fact that you get to
choose among millions of JDBC drivers). I do believe we can make all
these things easier (like Nick said, understand Rails db configs better,
and things like that), but I don't want to let it get in the way of
extensibility.
I guess I'm coming across as elitistic in this mail, but I truly believe
in not tying the hands of the power users.
--
Ola Bini (http://ola-bini.blogspot.com)
JvYAML, RbYAML, JRuby and Jatha contributor
System Developer, Karolinska Institutet (http://www.ki.se)
OLogix Consulting (http://www.ologix.com)
"Yields falsehood when quined" yields falsehood when quined.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
