1. 12
  1.  

  2. 5

    To be clear, it will be included in the default Gemfile; if you want to use it with an app you upgrade, you’ve gotta include it yourself, and if you don’t want it, you can just not have it in your Gemfile.

    1. 3

      just wait for the huge flood of issues related to js globals sticking around between page loads, js memory leak issues which don’t manifest until you take reloads out of the equation. Not saying pjax is not a good idea, but it isn’t magic fairy dust you sprinkle and things get faster. There are a certain class of issues that you didn’t need to be aware of before which you now do.

      1. 1

        there are already a bunch of people trying and fixing this, there were a bunch of issues, PR and mostly fixes just today.

        Certainly not production ready, true, but for pet projects, why not? :)

      2. 1

        This is one more thing that makes me eager to play with Rails 4! Matter of days now before I try it…

        1. 2

          You can try this gem today. Don’t need to wait for Rails 4.

          1. 1

            Anyone knows if there will be a beta build before the end of the year by any chance? Not that I need one to start playing around with it, just curious.

            1. 2

              We really want to have it out by the end of the year, yes. We’re actually pretty close, there’s just a few things blocking release now. All the major parts are in place.

              1. 1
                Awesome!

                Will sure try this soon and get my hands dirty!

          2. 1

            Is this Rails-only?

            1. 1

              Nope, it’ll work with any web framework, Ruby or not. It is maintained by rails-core and will ship by default with Rails 4, though.