@andre1sk I’ve merged your thread with the existing one 
With regards to Turbolinks, I actually quite like it (with Rails anyway) - it helps give the site an app feel. You can see it in action on a Rails site here (only on info, photos, and want more pages - the forum is not Rails) and some cat pages like here.
I’ve been toying around with a turbolinks/react apps lately. So far it seems quite solid. Turbolinks makes all the crud stuff seem snappy and react allows for the higher fidelity UI to be well designed and sprinkled throughout the app. It has pain points, but far fewer pain points then going full SPA.
If enough folks are interested in this I would be more than happy to extract a demo app out of my project.
This sounds pretty cool. Currently I’m playing with vue.js because it plays well with the rendered DOM.
But I’m very interested in a demo app, or more information
Would be really cool
[quote=“nerdyworm, post:14, topic:1091”]
It has pain points
[/quote] What would you consider to be the biggest pain points?
I would also like to see a demo how you integrated turbolinks and react into phoenix without having a SPA.
How does it perform with phoenix? Done any timings with Chrome’s network graph or so? Any integration issues? Any CSRF issues? Etc…?
As promised a Phoenix, Turbolinks, React, Redux, and Immutable.js example. Redux and Immutable are not a requirement for this setup, but they make frontend work a tad more enjoyable for me
source: GitHub - nerdyworm/returb: Phoenix, Turbolinks, React.js, Redux, Immutable.js example app. · GitHub
demo: https://sleepy-shore-92135.herokuapp.com (disclaimer: user editable content on the internets)
Pain Points/Things I haven’t figured out:
I do not have that much experience with React and elixir. I could be doing it totally wrong. If I am please help 
If there are any questions just ping me and I’ll be happy to help.
Cheers,
Ben
Any one tried Morphdom? GitHub - patrick-steele-idem/morphdom: Fast and lightweight DOM diffing/patching (no virtual DOM needed) · GitHub
Supposedly simple way to update parts of DOM preserving states like input cursor positions
As described in this well written blog post: Accelerate your developer workflow | Namespace
It feels like I’m seeing more of the “replaced react with traditional rails/turbo-links” type of posts suggesting web-dev is coming round full circle:
Early 2000’s.
Full page refresh is the standard. Works great.
Sprinkle in a little js. Works good.
Add more js, jquery mess. Not so good.
SPA everything. Explosion of frameworks and tools. Total confusion, increased development time.
Now:
No more SPA. Go back to full traditional full page refresh. Hey, still works great!
Now add back a little js…
(continue…)
