Hi,
I have to disagree with what you are saying.
I work for a database vendor and love the Ruby language. I have tried
tirelessly to bring the two together, but with no avail until JRuby
came along. The reason is mainly due to what our customers deem
acceptable. Virtually all our customers are Java shops, but will
accept Perl or Python for scripting. With JRuby it allows me to use
the language of my choice, and deploy it on the platform of our
customers choice. We all win.
Another reason. At present we provide a native, ODBC, JDBC or .NET
database drivers. Running with MRI means using ODBC (unless I was to
write my own DBD wrapper of the native drivers). Anyone who has used
ODBC via Ruby would know that it is not the best method of accessing a
database. Using JRuby allowed me to utilise the JDBC drivers, although
I still chose to go via the dbd-jdbc route, so not to pollute my Ruby
code with to much Java :-) This has proven to be far less painful
than ODBC, and the performance of the database access has proven to be
so much better, 2x-4x at least.
For me, JRuby and IronRuby are enablers for the Ruby world to enter
the enterprise and not be seen as a secondary language.
They give you more options to expand your business. Now you can
package that application from the cloud you developed and sell it for
use internal to the enterprise.
Regards
Matthew Winter
On 29/07/2009, at 9:45 AM, Joseph Pearson wrote:
> There's no doubt that JRuby is an impressive technological
> achievement, but with her mission, she's no friend of ours. Right now,
> Ruby (and Rails) is our competitive advantage. We shouldn't be
> worrying about how to get Ruby into enterprise. We should be worrying
> about Ruby getting into enterprise.
>
> All this stems from a misguided empathy as developers for our brothers
> and sisters stuck in enterprise. Stuck with awkward languages, copycat
> frameworks, dubious projects and secure, well-paid jobs. On average
> they're earning two or three times what we are, for work half as
> dangerous. If they want to share our good fortune, they can have the
> guts to make the jump. Or they can suck it up in Java/.NET/PHP.
>
> Does Ruby need this? Maybe, if it wants to win the popularity contest.
> But we have no great investment in that. Our investment is in the
> awesomeness of our community, which these efforts ("let's double the
> size!") throw into question. Don't forget: this is business. And
> that's your Wednesday morning rant. :)
>
> - J
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---
