4 ms·
Very true, but that's a frontend problem, not a rails problem.
by amrocha 4y ago
Very true, but that's a frontend problem, not a rails problem.
- jeremyjh 4y agoThese problems are always more common in server-rendered apps though, because front-end state is always a patchwork. And the Rails developers and community have a strong preference for this architecture.
- VWWHFSfQ 4y agoI observe the exact opposite. Server rendered UIs are far more often times up to date than client rendered apps.
- amrocha 4y agoI can't think of a single website that's real time and server rendered
- UlisesAC4 4y agoI do not have examples with me. But anything built with Elixir Liveview will be server rendered and will also be real time, with some gotchas though. https://github.com/phoenixframework/phoenix_live_view https://github.com/phoenixframework/phoenix_live_view
- jeremyjh 4y agoIts not exactly server rendered, though. After the first page view all the server is rendering are json graphs of dom diffs to be applied by the client application. If you use the routing features then technically its an SPA.
- gls2ro 4y agoMind you some parts of Github FE are React https://twitter.com/rauchg/status/1591464351990697984?s=46&t=MBvUO3Qs3QEK_GU1anYaZQ https://twitter.com/rauchg/status/1591464351990697984?s=46&t...
- int_19h 4y agoThe upside is that you can link just about anything in GitHub, and those links work consistently and point at the exact right content. This is much less common with SPAs.
- amrocha 4y agoSPA =\= client rendering
- jeremyjh 4y agoI agree its a valid criticism of parts of the ecosystem, but a lot of people these days are using next.js, nuxt.js or sveltkit and those give you easy patterns to follow so that all those things work, basically for free. SPAs are better now than they were just a few years ago.