News for hackers. Stuff that matters.
Re:Turbolinks for Rails (like pjax) by mmahemoff on Wednesday September 26, 2012 @03:46PM (#4577601)
So glad this will be default in Rails. I spent ages building a custom version of the same kind of PJAX framework, using headers to transmit flash messages, interpreting XHR calls in new and exciting ways, etc. It really needs to be standardised for modern web apps.

If Rails 4 is all about PJAX, my hope for Rails 5 is it's the one that embraces fat-client JS apps and exposes JSON services in a standard way, so they can easily be consumed by convention-based frameworks such as EmberJS.

Re:Turbolinks for Rails (like pjax) by joshpeek on Wednesday September 26, 2012 @04:50PM (#4577962)
> my hope for Rails 5 is it's the one that embraces fat-client JS apps

Pretty sure DHH would say not a chance.

Re:Turbolinks for Rails (like pjax) by dhh on Wednesday September 26, 2012 @05:21PM (#4578123)
Rails is great for fat-client JS apps as it stands today. Everything on the controller and model side of things makes for a wonderful backend for fat-client JS apps.

But if you're going to use Rails for the view, the focus will remain on making Basecamp-style apps (turbolinks, russian caching dolls, etc).

Re:Turbolinks for Rails (like pjax) by mmahemoff on Wednesday September 26, 2012 @05:20PM (#4578120)
I dont know. DHH has shown tremendous capability to say out with the old when he comes around to a viewpoint. And the old model of UI logic on the server is already in the phase of a slow decline at this point, imo.
Re:Turbolinks for Rails (like pjax) by amalag on Thursday September 27, 2012 @09:28AM (#4580546)
He is not into client side javascript yet. https://twitter.com/agd108/status/211115804882763776

I was asking him about http://joosy.ws. I was excited about their approach of tying the client side javascript UI into rails. Not just using another generic javascript UI framework and using REST models, but tying into the models of Rails and then making an intelligent linkup to the javascript front end. I think the approach could be the future.