On Aug 16, 7:55 am, Marnen Laibow-Koser <rails-mailing-l...@andreas- s.net> wrote: > It's Java. This is both an advantage and a disadvantage: you already > know about the advantages, but server-side Java can be hard to set up > for Web stuff. Personally, I'm using Ruby Enterprise Edition on many of > my servers, which gives better performance but without the hassle of > JRuby.
JRuby works fine as a Mongrel process (and if you turn on threadsafe mode in Rails, your entire site can be a *single* process). There's also the glassfish gem, which allows one-command deployment of an entire app, all in a single process. I think the difficulty of setting up JRuby on the server has been vastly overstated. $ gem install glassfish $ glassfish -e production <appdir> That's it. http://blog.headius.com/2009/04/apache-jruby-rails-glassfish-easy.html > > I man > > it's possible to use it with rails now, and JRuby is what's used by > > default in netbeans (which is the ide I think I've settled on). > > That is a bad reason to pick JRuby. Anyway, you probably shouldn't be > using Netbeans: it's a good IDE, but not for Rails. It's stupid enough > not to pick up generators properly, and in my experience, it doesn't > integrate all that well with Rails anyway, although I may try it again > in a year or two. There's actually a number of people that like NetBeans (or one of the other IDEs) a lot for Rails work. And of course if you're working with several languages, it does a very good job. > Anyway, I would urge you (especially at first) not to use an IDE for > Rails. IDEs are great for heavy Java frameworks where there are lots of > config files to automatically generate, but I do not believe they are > necessary -- or even desirable -- for Rails. Use a good editor such as > KomodoEdit (my current choice), TextMate, or jEdit and a bunch of > terminal windows. If you use an IDE for Rails you'll actually be making > your life harder. I don't think that's true. But it's a matter of opinion. Even if you don't use those IDEs as anything more than editors, they're very nice editors. > As far as the language is concerned, no. As far as Web server setup is > concerned, yes, very much. > > Note: the server setup can actually be an advantage if you already have > a Java setup that you want to integrate with. I don't, so I'd rather > not deal with Java servlet containers. You don't have to deploy to a Java servlet container, and for typical Rubyists we actually recommend using one of the non-servlet options. - Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
