Comments on: JRuby’s Future at Engine Yard

By: atejip

atejip — Mon, 06 Jun 2011 08:00:00 +0000

Thanks for your nice suggestion.

http://www.ateji.com

By: Jerome Louvel

Jerome Louvel — Thu, 17 Sep 2009 09:39:51 +0000

Hi Charles,

We which you good luck with JRuby at your new home.

Regarding the support for REST in JRuby, I suggest that you have a look at our Restlet Framework (http://www.restlet.org) which has support for JAX-RS in addition to its more powerful Restlet API and is available in several editions: JSE, JEE, GAE, GWT and Android.

We would be happy to support you in this effort.

Best regards,
Jerome Louvel
–
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com

By: What's New: Fresh Releases and Oh Right, a New Gig

What's New: Fresh Releases and Oh Right, a New Gig — Thu, 27 Aug 2009 20:11:36 +0000

[...] So, after a long, busy summer, I’m finally back onto support of the various bits for JRuby web application development (meaning Warbler and JRuby-Rack). I’m pleased to announce the 0.9.5 release of JRuby-Rack and the 0.9.14 release of Warbler! All of this brought to you courtesy of Engine Yard, my new employer! [...]

By: While away, starting with the hot-off-the-press part - - Technology

While away, starting with the hot-off-the-press part - - Technology — Tue, 04 Aug 2009 20:00:41 +0000

[...] have Java EE 6 support and recent GlassFish v3 as the default (Milestone 1 is just out). • JRuby guys moving to EngineYard (and confirming the GlassFish praises). • GlassFish v2.1 patch 3, for paying customers. • [...]

By: Leah Silber

Leah Silber — Tue, 04 Aug 2009 16:46:58 +0000

Hi Phred,

Engine Yard is indeed continuing to fund Rubinius development. The two full time developers on the project, Evan Phoenix and Brian Ford, are still very much at work and making progress :)

By: Phred

Phred — Tue, 04 Aug 2009 16:37:15 +0000

How does this impact Rubinius? Hoping that EY continues to fund Rubinius development.

By: cnutter

cnutter — Tue, 04 Aug 2009 07:57:24 +0000

That may be the case, but the purchaser doesn't simply throw a dart at a board. They measure reliability, supportability, TCO, ROI, TTM. Rails covers a number of those, and a commercially-backed JRuby can cover most of the others. And I think we've shown that JRuby is a strong, viable technology made stronger by the backing of a world-class Ruby and Rails company.

However, I'd love to talk with you offline about your theories on adoption. I'm sure we could learn from you and you may be able to learn from us. Our goal is to make JRuby the best JVM language and runtime we can possibly make it, and we'll leave no stone unturned along that path. Feel free to email me directly.

By: cnutter

cnutter — Tue, 04 Aug 2009 07:51:46 +0000

I should also mention that we have the deepest respect for Sun and loved working with them. They helped teach us the value of the developer, and helped us realize that technology decisions are made (and should be made) from the bottom up. We look forward to continuing to make JRuby the "developer's best friend", just like Ruby is a language "optimized for programmers happiness."

By: cnutter

cnutter — Tue, 04 Aug 2009 07:51:04 +0000

By: Roderick van Domburg

Roderick van Domburg — Tue, 04 Aug 2009 07:48:37 +0000

In my experience the barrier to enterprise acceptance lies with purchasing divisions. Developers can be hyped up about technology, but if you or some champion don't manage to sway purchasers then it'll never make it into enterprise production.