Hotwire Demystified - Jamie Gaskins

DHH stunned the Rails world with his announcement of Hotwire from Basecamp. Even folks in the non-Rails web-development community took notice.
In this talk, you will learn about the building blocks of Hotwire and how they compose to create a streamlined development experience while writing little to no JavaScript.

[@joe_rogan]

Great presentation. Keep it up! 💪

[@lexalexander9334]

Great impartial talk Jamie. Love how you explained the tradeoffs of each approach.

[@abdullahbarrak8618]

thanks, concise helpful presentation.

[@ginocapio]

Thanks! 🙏

[@SupeRails]

Is there any way to see a working version of the code that is presented?

[@arthurcheek5634]

Thankyou!

[@haroldpepete]

Great video, i have one question, what is the hotwier behavior between url change? you have to load a entire page in html main request!

[@SupeRails]

7:58 that syntax does not work...

[@_eddbot_]

For anyone else having the same issue I had to change the id in the turbo frame to use _underscores_, rather than hyphens-

[@purelydef9073]

No idea why rails has to be so absurdly complicated. In react, you never once have to think about the details of what’s going on in the AJAX requests because all that detail is abstracted away from developers and it just.. works. Having to understand all the nuances of low level details just to write a front end in exchange for not having to write JavaScript is NOT a good trade off at ALL. That’s like saying we can write all our clientside code in assembly but at least there’s no JS!

[@rumble1925]

You should try building a full stack app with both approaches and you will realise that Turbo gives you much better dx and abstracts away more implementation details than react spa’s do.