hotwire-rails
turbo
hotwire-rails | turbo | |
---|---|---|
98 | 145 | |
960 | 6,424 | |
- | 0.8% | |
3.2 | 8.7 | |
over 2 years ago | 10 days ago | |
Ruby | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hotwire-rails
- It's not Ruby that's slow, it's your database
- Howire Not Working after deploying to Heroku
-
What's New in Rails 7
Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.
-
Ask HN: What tech stack would you use to build a new web app today?
For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."
https://htmx.org/
https://hotwired.dev/
- Ask HN: Do we need JavaScript web frameworks?
-
anyone have full tutorial how to upgrade from rails 6.1 to rails 7 ?
For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).
-
Ask HN: What are you favorite goto frameworks when writing Web Aplications
I was recently interested in similar topic. Here are 3 similar solutions I found:
* https://htmx.org/
* https://unpoly.com/
* https://hotwired.dev/
My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:
* https://htmx.org/essays/hateoas/
* https://htmx.org/essays/locality-of-behaviour/
-
Hotwire isn't only for Rails
At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.
-
How do you handle views?
I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).
- Why learn Rails as a frontender?
turbo
-
Turbo Streaming Modals in Ruby on Rails
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.
-
Htmx vs. React: A Complete Comparison – Semaphore
https://github.com/hotwired/turbo
- Turbo 8 has been released
-
What is JSDoc and why you may not need typescript for your next project?
Turbo 8 remove typescript without using JSDOC
-
Coming to grips with JS: a Rubyist's deep dive
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
-
Improving a web component, one step at a time
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.
-
Mastering Rails Web Navigation with link_to and button_to Helpers - Part 2
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.
-
Why you should choose HTMX for your next project
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!
-
JavaScript First, Then TypeScript
Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.
-
Rack Attack – Rails Tricks
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/
What are some alternatives?
htmx - </> htmx - high power tools for HTML
SvelteKit - web development, streamlined
Turbolinks - Turbolinks makes navigating your web application faster
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
Svelte - Cybernetically enhanced web apps
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
inertia-laravel - The Laravel adapter for Inertia.js.