Reminds me of smalltalk. Interesting to see something like that make its way to the web.

There was pharojs and amber, but they were lackluster.

This is also true of REST requests. They're not scoped to the user by default. In fact, Rails doesn't even have the concept of a user by default.

The argument against using actioncable because it doesn't scope to users by default is roughly akin to arguing against rails in production because rails doesn't even know what a user is by default.

They don't really have any overlap.

Hotwire is for replacing frames with content when navigating through anchors or form posts.

StimulusReflex is performing RPC, then diffs the old page and the new page, updating changed elements.

One difference is that liveview / reflex are stateful whereas Hotwire (turbo) is not. This has varying performance implications. Turbo will do repeat work server side and payloads will typically be bigger, however development may be simpler due to lack of state and memory usage server side may be lower.

Turbo also has the possibility to gracefully degrade when js is not available (although I doubt this will be taken advantage of much in practice).

This is a great point. Plus not all platforms, hosts, and proxies for that matter will allow web sockets.

Especially for an established rails app, allowing web sockets can require architecture changes.

It's not official, but it may as well be. Fantastic library.

I would say a lot of people disregard internet speeds when creating websites. Just check the source of any random website, and you're going to see jquery loaded, where it's either not being used at all, or using a single function in the entire library.