|
Re: JRuby on Rails: msg#00049lang.jruby.user
On Tuesday 21 February 2006 02:35 pm, Nick Sieger wrote: > Do you have a running list of the major roadblocks that exist for running > Rails? I'm definitely interested in this enough to potentially carve some > time in the near future to work on it. What would it be best for me to > start playing with? Really it comes down to finding "small interpreter failings". Rails really stresses JRuby. Pick a rails thing (I did *some* work toward getting webrick running with an "empty app"), and run it. When something fails, figure out why by digging through the Ruby code until you can narrow the failure down to a small case. The vast majority of these turn out to be easy to fix, but you'll spend hours trying to make a small example of it. David > > Cheers, > /Nick ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | JRuby on Rails: 00049, Nick Sieger |
|---|---|
| Next by Date: | Re: JRuby on Rails: 00049, Ahmed Mohombe |
| Previous by Thread: | JRuby on Railsi: 00049, Nick Sieger |
| Next by Thread: | Re: JRuby on Rails: 00049, Ahmed Mohombe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |