cable-streams
turbo
| cable-streams | turbo | |
|---|---|---|
| 1 | 155 | |
| 26 | 6,955 | |
| - | 0.8% | |
| 0.0 | 8.0 | |
| over 2 years ago | 4 days ago | |
| TypeScript | 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.
cable-streams
-
Custom Turbo Stream Actions
Turbo streams with Stimulus Controllers give us enough power to achieve custom actions. Without further dependencies. If you use CableReady anyway, then have a look at this package from the wonderful Marco Roth that enables you to use the cable ready operations with turbo streams.
turbo
-
Less Htmx Is More
There are two sides to the argument which I think should be treated separately: a) Is it a good idea overall? and b) is htmx implementation good enough?
a) I think so, yes. I've seen much more spa that have a completely broken page navigation. This approach does not fit all use cases, but if you remember that the whole idea of htmx is that you rely on webserver giving you page updates as opposed to having a thick js app rendering it all the way it makes sense. And yes, js libraries should be wrapped to function properly in many cases, but you would do the same with no react-native components in any react app for example
b) I don't think so. htmx boost functionality is an afterthought and it will always be like this. Compare it with turbo [1] where this is a core feature and the approach is to use turbo together with stimulus.js which gives you automagical component life cycle management. Turbo still has it's pains (my favorite gh issue [2]), but otherwise it works fine
[1]: https://turbo.hotwired.dev/
-
Type-Casting Doubt: How A TypeScript Re-Migration Revealed The Truth About Turbo
The TypeScript configuration used in previous attempts was fundamentally flawed. From tsconfig.json prior to removal in commit 0826b8152c0e97f19d459c1a1c364fa89cc62829
-
Types are the basic tool of software design
https://github.com/hotwired/turbo/pull/971/files
- Turbo – Single-page web application without having to write JavaScript
- The speed of a single-page web app without having to write any JavaScript
-
Superglue vs. Hotwire for modern frontend development
Turbo
-
Playing around with Hotwire ⚡️
As you can see in the example above, I'm using Turbo Frames to give a single-page application feel, while not having to write any JavaScript.
-
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 are some alternatives?
hotwire-chat - Hotwire Chat is a demo Ruby on Rails web application built with Hotwire.
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
turbo_power - Custom Actions power-pack for Turbo Streams
htmx - </> htmx - high power tools for HTML
turbo_ready - Take full control of the DOM with Turbo Streams [Moved to: https://github.com/hopsoft/turbo_boost-streams]
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)