4 ms·

This will prevent running JRuby 9000 in (today's) Google App Engine. The project has been drifting away from App Engine support for some time now. See #2304.

by mdavidn 11y ago

This will prevent running JRuby 9000 in (today's) Google App Engine. The project has been drifting away from App Engine support for some time now. See #2304. https://github.com/jruby/jruby/issues/2304 https://github.com/jruby/jruby/issues/2304

dragonwriter 11y ago
> This will prevent running JRuby 9000 in (today's) Google App Engine. It'll prevent running it on the current Google App Engine Java Runtime. It won't, AFAICT, prevent running it in a Google App Engine Managed VM, which is an option on today's Google App Engine.
- mdavidn 11y ago
  True, but many teams running Ruby in Managed VM will use opt to run YARV directly.
chrisseaton 11y ago
There's a pure-Java fallback that has most of the same functionality. But if you wanted precise POSIX function calls you probably weren't running on App Engine anyway.
- jshen 11y ago
  Have you tried the pure-Java fallback on App Engine? I tried it for JRuby 1.7 and it didn't work. I haven't tried yet with 9000, have you?
  - headius 11y ago
    We welcome GAE users of JRuby but they never seemed to be a big segment of the community. And we continue to maintain non-native IO and process logic for limited environments. If that is not sufficient for GAE, we'll work with you to make it so.
    - jshen 11y ago
      Jruby 1.7 simply doesn't work in GAE, and maybe it's not worth making it work there, which I would understand. I opened an issue a while ago (https://github.com/jruby/jruby/issues/2304 https://github.com/jruby/jruby/issues/2304) and I spent about a week trying to fix it. Each time I fixed one issue another one popped up and I gave up after hacking up JRuby beyond my comfort level. Edit: I just want to stress, the JRuby team is amazing, and I've always been impressed with the responsiveness and openness of the team. This comment isn't meant as a critique in anyway, just a statement of fact with my experience trying to run JRuby on app engine.

by mdavidn 11y ago

dragonwriter 11y ago

> This will prevent running JRuby 9000 in (today's) Google App Engine. It'll prevent running it on the current Google App Engine Java Runtime. It won't, AFAICT, prevent running it in a Google App Engine Managed VM, which is an option on today's Google App Engine.

mdavidn 11y ago
True, but many teams running Ruby in Managed VM will use opt to run YARV directly.

chrisseaton 11y ago

There's a pure-Java fallback that has most of the same functionality. But if you wanted precise POSIX function calls you probably weren't running on App Engine anyway.

jshen 11y ago
Have you tried the pure-Java fallback on App Engine? I tried it for JRuby 1.7 and it didn't work. I haven't tried yet with 9000, have you?
- headius 11y ago
  We welcome GAE users of JRuby but they never seemed to be a big segment of the community. And we continue to maintain non-native IO and process logic for limited environments. If that is not sufficient for GAE, we'll work with you to make it so.
  - jshen 11y ago
    Jruby 1.7 simply doesn't work in GAE, and maybe it's not worth making it work there, which I would understand. I opened an issue a while ago (https://github.com/jruby/jruby/issues/2304 https://github.com/jruby/jruby/issues/2304) and I spent about a week trying to fix it. Each time I fixed one issue another one popped up and I gave up after hacking up JRuby beyond my comfort level. Edit: I just want to stress, the JRuby team is amazing, and I've always been impressed with the responsiveness and openness of the team. This comment isn't meant as a critique in anyway, just a statement of fact with my experience trying to run JRuby on app engine.