Hey all, at first I want to say "Hi!" - I am Tobi, 22 year old Software Engineering student from Germany but currently doing an ERASMUS student exchange in Sweden. I'm currently refactoring the hacketyhack editor and hopefully will request feedback on that soon, if you're curios however the current state of the art can be found here: https://github.com/PragTob/hacketyhack Now for hackety-hack.com I just played around a little and noticed that I need a JSExecution Environment, so far so good. I'm running Linux Mint 11. However installing SpiderMonkey didn't help and I ended up adding the "therubyracer" gem to the Gemfile. But I don't want to unnecessarily change the Gemfile, however I think it would be good to add a JSExecutionEnvironment to the Gemfile so potential contributors don't run into this problem. What do you think? Cheers, Tobi
Weeeeeell there's some discussion within Rails about this. Read this ticket, but our own jrgifford: https://github.com/rails/rails/issues/2963 and its referenced https://github.com/rails/rails/pull/3619 I'd like to do something that will end up being compatible with what they do. It seems like they're going to wait for exec.js to get better. So I think the best solution is to add therubyracer with :platform => :linux or whatever. And a comment noting to take that out when execjs improves. But I just quickly re-read the tickets. Check it out, and then feel free to do what you think is best.
My take from issue 2963 is that in the Rail's opinion, there is a hesitation to demand a specific JS environment for any specific platform. OTOH, we're at a higher (lower?) level than Rails base, and for Hackety (and Shooes?) to demand a specific JS environment doesn't sound unreasonable. I say this in relationship to the packager/installer for Shoes/Hackety, which can/does install any necessary dependencies. The discussion on issue 2963 seems to resolve into two options : 1). Require one of many separate libs depending entirely on platform (including Jruby) -OR- 2). Require Node.js everywhere and just depend on it flatly. Anyone for answer 2 w.r.t Hackety/Shooes? Peter Fitzgibbons (847) 859-9550 Email: peter.fitzgibbons@gmail.com IM GTalk: peter.fitzgibbons IM AOL: peter.fitzgibbons@gmail.com On Wed, Nov 23, 2011 at 9:47 AM, Steve Klabnik <steve@steveklabnik.com>wrote: > Weeeeeell there's some discussion within Rails about this. Read this > ticket, but our own jrgifford: > https://github.com/rails/rails/issues/2963 and its referenced > https://github.com/rails/rails/pull/3619 > > I'd like to do something that will end up being compatible with what they > do. > > It seems like they're going to wait for exec.js to get better. So I > think the best solution is to add therubyracer with :platform => > :linux or whatever. And a comment noting to take that out when execjs > improves. But I just quickly re-read the tickets. Check it out, and > then feel free to do what you think is best. >
#2 is sorta the default assumed state. The Hackety site only supports Ruby 1.9.2, but I _would_ like to move it to Rubinius eventually. So JRuby isn't a problem. We also have Heroku to consider... I develop primarily on OSX, so whatever works for you Linux guys is fine by me.
Hi, thanks for the answers and sorry for my late answer! I know that heroku has some own version of the rubyracer gem (https://github.com/aler/therubyracer-heroku) with a precompiled binary for their platform, so shall I add that for production? Hm however we didn't need it until now so maybe not... Other quick question, the gem "therubyracer", :platform => :linux should be in the group :development, :test right? If so I'll add it later :-) Cheers everyone! Tobi On 11/24/2011 05:55 PM, Steve Klabnik wrote: > #2 is sorta the default assumed state. The Hackety site only supports > Ruby 1.9.2, but I _would_ like to move it to Rubinius eventually. So > JRuby isn't a problem. > > We also have Heroku to consider... > > I develop primarily on OSX, so whatever works for you Linux guys is fine by me.
Node.JS in some way has Heroku support now. http://devcenter.heroku.com/articles/node-js http://blog.heroku.com/archives/2011/6/22/the_new_heroku_2_node_js_new_http_routing_capabilities/ Not sure how that plays into this thread? Peter Fitzgibbons (847) 859-9550 Email: peter.fitzgibbons@gmail.com IM GTalk: peter.fitzgibbons IM AOL: peter.fitzgibbons@gmail.com On Sat, Nov 26, 2011 at 4:17 AM, Tobias Pfeiffer < tobias.pfeiffer@student.hpi.uni-potsdam.de> wrote: > Hi, thanks for the answers and sorry for my late answer! > > I know that heroku has some own version of the rubyracer gem > (https://github.com/aler/therubyracer-heroku) with a precompiled binary > for their platform, so shall I add that for production? Hm however we > didn't need it until now so maybe not... > > Other quick question, the gem "therubyracer", :platform => :linux should > be in the group :development, :test right? If so I'll add it later :-) > > Cheers everyone! > Tobi > > On 11/24/2011 05:55 PM, Steve Klabnik wrote: > > #2 is sorta the default assumed state. The Hackety site only supports > > Ruby 1.9.2, but I _would_ like to move it to Rubinius eventually. So > > JRuby isn't a problem. > > > > We also have Heroku to consider... > > > > I develop primarily on OSX, so whatever works for you Linux guys is fine > by me. > >
We do not currently need it on production. We're running on Cedar, which has that stuff already.