Phoenix specifically doesn't work like turbolinks. LiveVIew in Phoenix uses a websocket to transport data, morphdom to patch the dom, and a light process on the server to manage state. It's as fast as the internet connection for insertions into a list. In fact it is quite capable of parallel data loading just like remix, and the server can work share in parallel across as many cores as you have available on the server.
> 2.5 GHz Quad-Core Intel Core i7 16 GB 1600 MHz DDR3
Obviously memory starts to be a constraint for doing anything meaningful, but you can squeeze a lot out of 32gb of ram.
[1]https://phoenixframework.org/blog/the-road-to-2-million-webs...
Remix makes things that were simple hard (apparently with the goal of doing _everything_ on the server again).
https://github.com/t3-oss/create-t3-app
I hadn't touched much webdev for a few years, the ecosystem / build tooling has gotten a LOT better. It's back to being fun and painless to spin up a new webapp.
Both got error, which seems to be due to next/next auth dependency breaking. So it's not that painless I guess.. I found this situation quite often with nextjs example template
T3 author is very responsive though, so my issue resolved quickly
The realtime aspect of what you are looking for is the hard part. The only options I know of are the remix stack above (you still have to do some extra plumbing), elixir/Phoenix (or other turbo links like options but most aren't fast enough). To do realtime updates natively you need to move to evented data front to back and that is a very big move away from models the way we normally think of them. Check out eventide or resolv.js.