This is one of the most exciting upcoming features for Turbo / Rails. It fits so well with why so many of us align with this framework. Great talk. Thank you 👏
It is true. But if you had experienced making a web page with ONLY HTML and CSS, turbo seams normal and fits perfectly. An HTML data attribute that function very well and no need to add JS complicity and event listener,..... extra stuff and cases that you need to monitor one by one. For me, writing web apps with Hotwire in Rails is the natural way of creating web application. No need for extra stuff. Or extra libraries.
Thanks for the amazing talk. I'm super exciting about Morphing. The more we stay way from JS code the happier and productive a programmer is. I thing morphing -if i understanding it correctly- it is a one action replace a few of stream actions. Because all what stream actions are doing are alteration to a section of a page. So instead of specifying the action name (update, replace,...) morph understand it a changing has happened and i will reflect that. Hope I understand it.
Very interesting talk. I'm looking forward to getting the chance to use this. A few questions pop to my mind that I'm sure I'll find out soon : What is the resource cost of sending the whole board to be morphed to a potentially large amount of concurrent users whenever someone changes something? Instead of each user refreshing their own board, each user is refreshing everyone's board. Also curious to find out how to preserve each user's context when a broadcast is triggered. E.g. not everyone may see the board the same way. Some will have different sorting or filtering, so it can't be a single view that's rendered and sent to everyone.
"preserve each user's context" - the issue you are describing is one of the exact issues with "turbo streams" (the "old" way) where the server uses websockets to broadcast the html to the "other users". In the new solution he's pitching, it looks like the server is only broadcasting a "touch" event to the "other users". Then the turbo javascript on each one of those pages will refetch the html specific to them (and have the new dom be morphed in). Then turbo exposes additional attributes (turbo data permanent) so that users' view doesn't get overridden with the new html.
Absolutely. I remember I was excited when I learned about Hotwire and Stimulus code from Basecamp and Hey web pages source code or web inspector. It is exactly the same I learned to code HTML and CSS in late 90s 😀 Simple, direct, accessible, free, and fun. Those were the days!
This is one of the most exciting upcoming features for Turbo / Rails. It fits so well with why so many of us align with this framework. Great talk. Thank you 👏
one of the best web app talks I have seen ... not just rails but in general ... less hype and very pragmatic
“It’s very hard to appreciate turbo as a newcomer” Agreed 👍 morph sounds amazing I can’t believe it’s the first time I heard about it
It is true. But if you had experienced making a web page with ONLY HTML and CSS, turbo seams normal and fits perfectly. An HTML data attribute that function very well and no need to add JS complicity and event listener,..... extra stuff and cases that you need to monitor one by one.
For me, writing web apps with Hotwire in Rails is the natural way of creating web application. No need for extra stuff. Or extra libraries.
Omg, I wanna use it now :D turbo streams are already epic, but this is next level :D
Awesome feature!!!❤
Thanks for the amazing talk.
I'm super exciting about Morphing. The more we stay way from JS code the happier and productive a programmer is. I thing morphing -if i understanding it correctly- it is a one action replace a few of stream actions. Because all what stream actions are doing are alteration to a section of a page. So instead of specifying the action name (update, replace,...) morph understand it a changing has happened and i will reflect that. Hope I understand it.
Very interesting talk. I'm looking forward to getting the chance to use this.
A few questions pop to my mind that I'm sure I'll find out soon :
What is the resource cost of sending the whole board to be morphed to a potentially large amount of concurrent users whenever someone changes something? Instead of each user refreshing their own board, each user is refreshing everyone's board.
Also curious to find out how to preserve each user's context when a broadcast is triggered. E.g. not everyone may see the board the same way. Some will have different sorting or filtering, so it can't be a single view that's rendered and sent to everyone.
"preserve each user's context" - the issue you are describing is one of the exact issues with "turbo streams" (the "old" way) where the server uses websockets to broadcast the html to the "other users". In the new solution he's pitching, it looks like the server is only broadcasting a "touch" event to the "other users". Then the turbo javascript on each one of those pages will refetch the html specific to them (and have the new dom be morphed in). Then turbo exposes additional attributes (turbo data permanent) so that users' view doesn't get overridden with the new html.
Excelente presentación!!!
WEB IS FUN AGAIN!
Absolutely. I remember I was excited when I learned about Hotwire and Stimulus code from Basecamp and Hey web pages source code or web inspector. It is exactly the same I learned to code HTML and CSS in late 90s 😀 Simple, direct, accessible, free, and fun. Those were the days!
RIP Redux/Context
Waiting for firefox😢
tl;dw - refresh page but do not scroll