Thomas Cannon

@fontawesome my kingdom (and recently broken wrist 😭) for official an Stream Deck pack 😭

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. thomascannon.me/guides/fixing-…

Every day is further proof that we simply need to use UTC across the board. No more timezones. They have played us for absolute fools

Cc @nateberkopec

Finally getting the chance to listen! it’s very funny that the frontend convo happened right before I published this guide 😂 thomascannon.me/guides/fixing-…

@jeremysmithco Well until Liminal ships at least 😄

@tcannonfodder Ha, that's right! We come to Twitter for work talk. 😂

@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

@tcannonfodder Oh, I meant to bring that up this morning, just slipped my mind! :) Yeah, I thought you'd like Nate's take there.

@_swanson @danecando You definitely aren’t alone in that feeling; I wrote 3K words with a bunch of source about this exact thing thomascannon.me/guides/fixing-… 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”

@danecando yeah I mean I dont think it's a skill issue per-say but more of a "if you go off the tracks, it's dicey" and "you may need to make large changes to your UX to fit into the tracks"

Wanted to share a struggle with Rails front-end: Working on adding Swiper (swiperjs.com/element) to our app. It has a really nice WebComponent and was easy to get added to our Hotwire app. Love using WebComponents for things like this because it fits so nicely with Hotwire ideas. Everything was working great, until a few hours later as I add more configuration and run into a case where the component assumes there is a traditional page load (vs a turbo drive visit) and gets into a weird state. So have to eject and write a Stimulus controller to manually init/destroy to fit Hotwire lifecycle. I was able to get it working and the code is Fine, but it's the kind of annoying thing that you'll run into when trying to interact with the wider web community. It really highlights some challenges: we have opted out of React/Vue so any of those components are off the table. WebComponents are what we want to use, but sometimes there are Hotwire-related quirks and edge cases (turbo visits, morphing, data-turbo-permanent) that break subtlety. So back to wrapping libs in Stimulus controllers. Not exactly something that sparks joy like the rest of Rails :(

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

@tcannonfodder another thing to consider, do you know that turbo provides a way to port rails app to a hybrid mobile app using strada and turbo native, would this approach work? would the interactions be the same or is this something that is not contemplated with this approach?

I saw this post and I loved it, designed especially for JS devs, could your app continue working if I disabled JS?🤣🤣

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 codepen.io/tcannonfodder/…

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 😄

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.

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. thomascannon.me/guides/fixing-…