masilotti.com VS turbo

If your like this approach to building hybrid native mobile apps, I highly recommend following Joe Masilotti at https://masilotti.com/

I only read three emails newsletters, and Joe’s is one of them because it’s roughly once per month and it keeps me current on all the things happening with Hotwire and Turbo Native apps.

And you're not wrong - there are very few resources available on Turbo Native development. My blog, workshop, and YouTube videos are practically the only things out there. And William Kennedy is sharing his process learning Android, which is helping fill that gap.

add contact links as well (LinkedIn, Github) (ex. https://masilotti.com/ )

update your website - make the site clean and direct about who you are, what you do, what you're looking for, and where you are (ex. https://masilotti.com/ )

be specific in your title & intro - "Junior Python/React Fullstack Dev" and "Locacted in Tulsa, Ok" mean more than "I thrive on challenges". What's the most important info about what you do and who you are? Make that first and prominent. (ex. https://masilotti.com/ )

add your photo in place of sonar. This site is selling your services and it gives more trust to have your face on your website. ex. https://masilotti.com/ ) You can move a block of text with skills below your "Hi, I'm Patrick" text.

Turbo Native in its current form requires a fair amount of iOS knowledge (and code!) to get working. I'm trying to fill that gap with my blog, workshops, and live streaming sessions. [1]

But it's no excuse for what this library could be if we invest more time into it. In an ideal world the library handles 90% of the boilerplate required to make an iOS app work. I'm talking authentication, pushing/presenting controllers, sensible defaults for Path Configuration, etc. All the stuff that I have to add to every single Turbo Native app I work with. (12+ since I last counted.)

Then devs can focus on differentiation and exciting features like push notifications, native integrations, fancy animations... while the core of the logic remains on the Rails app.

I'm hoping that getting more maintainers (like me!) on the repo will help kickstart this. And I'm excited to see more interest on both HN and Twitter in the framework.

[1] https://masilotti.com

I blog about Turbo Native and run the monthly ⚡️ Hotwire dev newsletter!

I also recommend checking out the docs for Stimulus and Turbo to familiarise yourself with all their features and the APIs used in this series.

https://github.com/hotwired/turbo

Turbo 8 remove typescript without using JSDOC

Experiment using Turbo to drive front-end behavior: "Turbo 7.2.0 (currently in beta) allows you to define your own Stream actions which can be any JS code you want. By combining a custom Stream action or two with web components, you can essentially drive reactive frontend behavior from the backend stupidly easily. Loooove it! 😍 […] For a turnkey example, you could check out https://github.com/hopsoft/turbo_ready " —Jared White on The Spicy Web Discord

This handles disconnection (as could be done by any destructive change to the DOM, like navigating with Turbo or htmx, I'm not even talking about using the element in a JavaScript-heavy web app) but not reconnection though, and we've exited early from the connectedCallback to avoid initializing the element twice, so this change actually broke our component in these situations where it's moved around, or stashed and then reinserted. To fix that, we need to always call addSparkles in connectedCallback, so move all the rest into an if, that's actually as simple as that… except that when the user prefers reduced motion, sparkles are never removed, so they keep piling in each time the element is connected again. One way to handle that, without introducing our housekeeping of individual timers, is to just remove all sparkles on disconnection. Either that or conditionally add them in connectedCallback if either we're initializing the element (including attaching the shadow DOM) or the user doesn't prefer reduced motion. The difference between both approaches is in whether we want the small animation when the sparkles appear (and appearing at new random locations). I went with the latter.

If you think you have seen enough Rails magic, you are mistaken my friend. Rails have a new trick up its sleeve: Hotwire. And with the magical Turbo tool that comes with it, you can create modern, interactive web applications with minimal, or sometimes no JavaScript at all, providing users with an incredibly smooth experience.

There is also Turbo and the frameworks who adopt them, Ruby on Rails, PHP Symphony and possibly others that solves the same issue in the same manner as HTMX. And the choice for HTMX is only a personal taste in this, but you should definitely learn about this, this is as cool as HTMX!

Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.

Turbo[0] has been solving this for years. Quite the contrary, front-end frameworks have started to think "sending JSON is good, but actually sending HTML could be great!".

DHH's presentation[1] during Rails World 2023 is quite interesting in that regard, I recommend you give it a go (start around minute 16). I am actually very excited with his vision of the web.

[0] https://turbo.hotwired.dev/