I wish more and more people see this video and this channel. This is the way to teach something. I can see how much hard work has been put into creating this lesson. And THANK YOU SO MUCH for that. It makes it super easy for people to understand the concept. You guys are great teachers. Thank you again.
gotta be honest man, this channel is a gold mine, HIGHLY underrated, this is by far the best channel to learn stuff online, the way you explain stuff, holy shit
I really hope this video and channel gain more traction. The teaching method is top-notch and it's evident a lot of effort went into creating this lesson. Thank you so much for making the concept easy to grasp. Your teaching skills are excellent. Many thanks again.
istg, ruby on rails has got this ahead for most, if not all, fullstack frameworks of different languages. i'd wished i'd work with ruby on rails sooner cuz woww! thanks for that nice hotwire in 6 minutes video, really makes me more inspired to use ruby on rails even more!
Just great ! That's how server-side frameworks try staying relevant in the age of Jamstack and native clients: find convoluted/complicated ways of justifying server-side UI generation. On top of that, overly complicating things buys job security for devs, what's not to like?
I originally learned Ruby & Rails via one of your courses back in 2014. I’m trying to write a site that has an audio player that I need to keep playing during page changes. I want the URL to update so that people can bookmark the page but so it only loads the full page if accessed from an external click. Is Turbo Drive the right tool nowadays?
And it pretends that the only reason people want to decouple Frontend and Backend exist is speed. That's not the case. I think it's not even the main reason in many cases.
@@hawa7264 If by speed they mean responsiveness I think it kinda is but is not the main reason (at least not for me), my main reason is that it is just natural to have the rendering engine at the front end while the data comes from the backend and render in a MVVM fashion. Rails developers I know want to solve everything with Ruby, as if it was a magic bullet. And their way of thinking is constrained to MVC. In real life (and in software) there is a tool for everything, it is awkward to try to solve every problem with the same framework/tool. Maybe hotwire is great, but it babysits developers to avoid JS when they shouldn't. It seems the time for fat frameworks (like angular or rails) is over.
I wish more and more people see this video and this channel. This is the way to teach something. I can see how much hard work has been put into creating this lesson. And THANK YOU SO MUCH for that. It makes it super easy for people to understand the concept. You guys are great teachers. Thank you again.
gotta be honest man, this channel is a gold mine, HIGHLY underrated, this is by far the best channel to learn stuff online, the way you explain stuff, holy shit
What an awesome and easy to understand overview. Can’t wait until I will start with your Hotwire course!
I really hope this video and channel gain more traction. The teaching method is top-notch and it's evident a lot of effort went into creating this lesson. Thank you so much for making the concept easy to grasp. Your teaching skills are excellent. Many thanks again.
I don't usually comment on videos but I wanted to say how clear and concise this video was. Many thanks!
This is literally the best video on this topic! Thanks so much for the simple explanation!!
istg, ruby on rails has got this ahead for most, if not all, fullstack frameworks of different languages. i'd wished i'd work with ruby on rails sooner cuz woww! thanks for that nice hotwire in 6 minutes video, really makes me more inspired to use ruby on rails even more!
Like many others, I found this video incredibly well put together and concise. Thank you so much, it was incredibly helpful!
Just great ! That's how server-side frameworks try staying relevant in the age of Jamstack and native clients: find convoluted/complicated ways of justifying server-side UI generation. On top of that, overly complicating things buys job security for devs, what's not to like?
thanks for the introduction!
Thanks for explain, make more sense to me now. 😍
Great video!
I originally learned Ruby & Rails via one of your courses back in 2014. I’m trying to write a site that has an audio player that I need to keep playing during page changes.
I want the URL to update so that people can bookmark the page but so it only loads the full page if accessed from an external click.
Is Turbo Drive the right tool nowadays?
Thank you so much, this is awesome!
Please create a Rails 7 tutorial playlist
I think that htmx makes hotwire mostly unnecessary.
all these sounds more complex than SPA. Maybe it is not. 🤔🤷♂️
And it pretends that the only reason people want to decouple Frontend and Backend exist is speed. That's not the case. I think it's not even the main reason in many cases.
@@hawa7264
If by speed they mean responsiveness I think it kinda is but is not the main reason (at least not for me), my main reason is that it is just natural to have the rendering engine at the front end while the data comes from the backend and render in a MVVM fashion.
Rails developers I know want to solve everything with Ruby, as if it was a magic bullet. And their way of thinking is constrained to MVC.
In real life (and in software) there is a tool for everything, it is awkward to try to solve every problem with the same framework/tool.
Maybe hotwire is great, but it babysits developers to avoid JS when they shouldn't. It seems the time for fat frameworks (like angular or rails) is over.