RailsConf 2016 - Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson

Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson
Learn how Turbolinks 5 enables small teams to deliver lightning-fast Rails applications in the browser, plus high-fidelity hybrid apps for iOS and Android, all using a shared set of web views.
SAM STEPHENSON
Help us caption & translate this video!
amara.org/v/J5Ci/

[@omarluq5313]

7 years later still an amazing talk and super influential! To think that I gave a knowledge transfer at work today saying exactly what Sam was saying all these years ago! Hotwire ❤

[@RezaaLenda]

One of the most amazing talks I've watched in a long time! 😊

Great talk indeed.

[@TheNavinsamuel]

Arguably one of the best tech talks I have heard in a long time!

[@fabriziobertoglio7342]

Thanks a lot, for this amazing talk and all your work in the last 10 years!

[@buildtolearn]

Very glad I found this. I just started playing around with Turbolinks in a NodeJS app I'm working on using AdonisJS, and it is really nice to work with! Indeed not everything needs to be an SPA. I'll be doing a lot more with it and sharing the work in videos for others interested. Thank you!

[@PeterLeder]

Yes, yes, yes. Thank you so much for this.

[@thebadtouch9460]

Great presentation.

[@rajdeepsinghbhatia6782]

Loved it!

[@sieuhaihuoc5554]

amazing talk. Thanks

[@tomasvalent3876]

really really good points

[@cuongdev]

Amazing!

[@Theschnaz21]

This is really good!

[@foobars3816]

Is this still possible? This would like not get approved for the App Store right as it steps around the review process. Is that correct?

[@justicerie]

Does anyone knows how to do the same with android studio? I'm a beginner, made a pretty cool rails app, installed turbolinks, but when it gets to Android studio, I get lost. And yep, I read the doc :D At least I tried!

[@WilkerLucio]

It's an interesting utility to leverage Rails apps to have an improved navigation experience, I just would not select this as a solution for a new product. I think there are better more modern approaches than what we used to do. You still are going to have to write Javascript, and this solution here seems to not deal with more complicated UI's. Look at React with React Native, using that you can build from web pages to real native components using the same technologies, and a lot of code can be shared between the clients. Look at the new concept of Demand Driven Architecture (check Falcor, Relay and Om.next), this provides a solution to have a single unified API that can handle all the clients at once with great performance, by delivering just the necessary data. Those ideas make it more efficient, more powerful and IMHO easier to develop.

[@perrywang3972]

Did you finished any complicated React Native project ? I have to say it's bad experience. Especially for even a little bit complex UI component. Basically you take your whole day to search at js.coach or github.

[@starpause]

I'm also curious how much actual code re-use it achieved between React Native and React applications. ReactXP would suggest not much, hence it's existance, and they themselves say "The authors of React use the phrase ~learn once, write anywhere~. With React and React Native, your web app can share most its logic with your iOS and Android apps, but the view layer needs to be implemented separately for each platform." Following that, maybe the real cost savings in running with the React technology family is not having to re-learn a front end approach/framework across platforms.

[@hugohouyez6656]

Nothing works here. I get a bunch of errors like 'Missing argument Label in call 'URL', Cannot convert value of type 'ViewController' etc ...

[@LauraKirby26]

Buuuut Turbolinks is still breaking my JQuery.... Anyone know of working demos/tutorials for Rails 5 and Turbolinks 5 with Jquery? @confreaks, Sam mentions that Turbolinks break JQuery but then he doesn't provide a solution.

[@kaspermeyer5049]

jQuery should work out of the box with Turbolinks 5, with one exception: The $( document ).ready(function() {...}); callback needs to be replaced with Turbolinks' own version: $( document ).on("turbolinks:load", function() {...}); I'm not completely sure, but you might also need to attach all events to the document like so: $( document ).on("click", ".some-class", function() {...}); To ensure the new DOM-elements swapped in by Turbolinks hits the event listeners.

[@LauraKirby26]

Thanks Kasper, you are correct here. One issue this presents, when using a front-end library, is modifying each and every $( document ).ready function. To the best of my knowledge, this means having to manually import the JavaScript, instead of relying on the gem, to make these adjustments. Have you found a more efficient way of resolving this issue?

[@kaspermeyer5049]

Yeah, that would be a problem. I haven't had this issue myself, but a solution would be to override the existing ready() function before importing the external libraries, with one that attaches the callback to a turbolink event listener instead. Like this: jQuery.fn.ready = function(handler) { return $(this).on('turbolinks:load', handler); }; or if you use CoffeeScript: jQuery.fn.ready = (handler) -> $(this).on 'turbolinks:load', handler I havn't verified if this actually works, but as long as you run that piece of code before importing your front end library, you should be all right, and hopefully you won't have to modify the existing code. Hope it helps :)

[@LauraKirby26]

Cool, I will try out this implementation. Thanks for passing along the additional article brandonhilkert.com/blog/organizing-javascript-in-rails-application-with-turbolinks/

[@pedrojosejimenezochoa6146]

Laura Kirby Thanks so much for the information

[@assaf416]

this is is boring..