This, 1000%. I still stand strongly behind CableReady being the better approach than Turbo
Even though I don’t use Updateable much, the reusability & extendability of CableReady’s foundation can’t be beat. https://t.co/WZwQQinhdR
(very) unpopular opinion: After spending some time with Turbo 8 Page Refreshes, I still find CableReady::Updatable's DX superior.
Why? Because you can specify directly in the view which parts of the page should be reactive, _without_ having to set up separate stream sources etc.
Episode 39 is in the queue! 📥 Nate Berkopec (@nateberkopec) joins us to talk about his consulting career, finding his niche in Rails performance, and what he's been up to most recently. Nate, thanks for all the insights you shared! 😊
https://t.co/JgSiyGa31c
@jeremysmithco Well I DID suggest we not talk about any work stuff so not your fault there 😂😂
But yeah! I’m just glad folks other than myself, especially high-level folks like Nate, are seeing the same problems I am
@_swanson@danecando You definitely aren’t alone in that feeling; I wrote 3K words with a bunch of source about this exact thing https://t.co/WZwQQinhdR
IMO Hotwire is such a footgun for the Ruby ecosystem at large because it causes this feeling of NIH & for us to “not play nice with others”
I’ll have more to show and a proper writeup soon, but it’s extremely cool that LittleCRM has replies & threading, with realtime updates. And because it’s CableReady/mrujs, I was able to reuse a ton of code & keep the cognitive load to a minimum
@rsamuelgarcia It's something not contemplated. Strada is the same classification of tooling as PhoneGap/React Native (IMO), which we've proven time and time again doesn't result in great user experiences. PWAs are making great strides, and if you need a native app the new frameworks are good
I'm 99% sure on this, but is this the only way to get as error-tolerant/JS-failing-resilient as possible *modal* dialogs? I know you can use the `popover` attribute; but in this case I *do* want these dialogs to explicitly be modal dialogs
https://t.co/xSFUXv384N
I’m not saying this is *the* option, but it is an option. And it’s my strongly recommended option—the one I believe to be the most robust and easy to use. Anyways; give it a read, chew on it, and let me know your thoughts 😄
I just published ~3K words + diagrams + code samples + demo videos on the frontend networking stack I’m choosing for Little CRM, and all my apps going forward.
https://t.co/WZwQQinhdR
Especially on the frontend, given Rails’s history of jettisoning multiple iterations while never having sat down and truly thought out how the code lives on the client side.