unpoly VS turbo-rails

I really like the potential for sending minimal document elements, though it seems like these features should be built into the browser. Unpoly, for example, has its own entire reimplementation of fetch():

https://github.com/unpoly/unpoly/blob/4854c7ccb268890a9522c6...

Do any browsers have the early workings of a native web application sdk?

The install notes here link to an issue specific to webpacker. Try that and see if it works?

True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.

Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb

So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.

Use this too: https://github.com/hotwired/turbo-rails

Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433

Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0

turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.

The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails