A similar alternative that does not rely on web sockets is <a href="https://htmx.org" rel="nofollow">https://htmx.org</a>. I have greatly enjoyed using it with some simpler web frameworks like <a href="https://javalin.io" rel="nofollow">https://javalin.io</a> to do some prototyping and smaller projects. I'm sure if someone made a plug and play UI library like material UI for Angular on top of htmx you could absolutely fly through MVPs.
I’ve been casually following turbolinks (now Turbo) for a while now, and I intend on using it in a future project.<p>Is anyone out there using turbo? Got any suggestions or tips?
I've always been hesitant with a introducing a websocket server into my rails application. If the websocket server goes down, you'll still be able to render the SSR-ed shell via the web server. Aren't we just introducing the data consistency problems into every HTML page that uses Turbo. Rails has celebrated its monolithic approach, but i just don't want to deal with websocket problems when what I want is truly a one person framework.