Ruby on Rails 4.0.0.beta1 released
21–30 of 91 posts
Re: Ruby on Rails 4.0.0.beta1 released
#22Sorry for the naive question... But does this help Heroku's woes?
Re: Ruby on Rails 4.0.0.beta1 released
#23What is the "Rails way" of doing AJAX calls and updating the DOM? I've been embedding Backbone views in the parts of my app that are the most interactive, but I feel like there's gotta be a better way.
Rails 4 uses turbolinks. It is a mechanism that instead of loading a new page loads up the HTML via AJAX and replaces the entire content of the page without reloading all the resources(css, js, etc...) So instead of having to deal with plenty of small ajax calls you just build an app as it would work in plain HTML and just use turbolinks to leverage AJAX.
Re: Ruby on Rails 4.0.0.beta1 released
#24does threadsafe and ruby 2.0 mean we can create multiple instances with something like unicorn without forking the entire codebase?
Ruby 2.0 still has the GIL so if you want to run a threaded web server you'll still need to be using rubinius or jruby.
Re: Ruby on Rails 4.0.0.beta1 released
#25Hello everyone! I am MEGA EXCITED for this release, as it's the first version in which I'm a committer. Wooo! In addition, 954 other intrepid Rubyists in total contributed to this release: http://contributors.rubyonrails.org/edge/contributors Please note that this is a beta, not an rc, so some things may be a bit wonky. Please file an issue on GitHub and I will do everything I can to help you help us iron out all the…
Re: Ruby on Rails 4.0.0.beta1 released
#26What is the "Rails way" of doing AJAX calls and updating the DOM? I've been embedding Backbone views in the parts of my app that are the most interactive, but I feel like there's gotta be a better way.
Others mentioned Turbolinks, but they forgot about remote_form_for and friends.
If you _are_ building a full JavaScript application, Ember.js works really well with Rails + ActiveModel::Serializers. There might be some rough patches until Ember hits 1.0 final, but most of the pieces are in place.
Re: Ruby on Rails 4.0.0.beta1 released
#27Re: Ruby on Rails 4.0.0.beta1 released
#28Earlier quoted context omitted.
Rails 4 uses turbolinks. It is a mechanism that instead of loading a new page loads up the HTML via AJAX and replaces the entire content of the page without reloading all the resources(css, js, etc...) So instead of having to deal with plenty of small ajax calls you just build an app as it would work in plain HTML and just use turbolinks to leverage AJAX.
Funny that ASP.NET had the same thing, called Smart Navigation, back in 2003.
Re: Ruby on Rails 4.0.0.beta1 released
#29Earlier quoted context omitted.
Ruby 2.0 still has the GIL so if you want to run a threaded web server you'll still need to be using rubinius or jruby.
Any reason ruby still has the GIL and not moved to a thread implementation?
Re: Ruby on Rails 4.0.0.beta1 released
#30Is there a Turbolinks equivalent for Django? Or something platform agnostic (I couldn't tell if that was the case with Turbolinks)?