Ah, thanks. I'm more on sysadmin side for my day job, and didn't even know about this. I'll have to keep it in mind as I've been dabbling with learning a modern web framework and React was a candidate.
Thanks - I hadn't even thought about that aspect, but it's definitely a problem I would run into. As popular as React is though, I'd assume there is a browser extension or something to support the workflow.
That's the plan. At the moment the web version is built using KnockoutJS which I wish I hadn't used so I'm looking to move over to React. Once I've done that I'll definitely share code between them.
Ideally this would work by setting up a private npm repo and then I can share components between the two.
None require React specifically, of course. I’m only referring to the dichotomy between server-rendered apps and apps with significant client-side interactivity.
That's interesting! Thanks for the link. Any other suggestions?
I'm honestly considering using React when I have the luxury of hosting on my own server. I find it difficult to go back to other templating systems after the nice 'componentized' approach of React. Hard to justify though.
We can also use React for that–the issue is the bundle size and it does not appear to be designed to share the DOM. I would love to see these smaller libraries document the process and best practices for using them within otherwise vanilla environments.
Thank you. I have been learning React lately (as a backend developer, I love it) and this will be helpful. I've considered using webpack or one of the competitors - there are so many that I've simply just avoided them until now.
None! Don't use these tools they massively complicate everything.
Single Page Applications were the wrong direction for us. Tens of megabytes of massive js libraries built using bundlers and minifiers and shims and whatnot, only to render something on the screen that would've been rendered with pure html using ssr.
Honestly I enjoy coding with React a lot. Components are a really robust way of reasoning about UI logic. But it's not worth the problems it solved.
The usecase for SPA's is really small. Maybe Slack should use React sure. But not all the other apps out there. Look at Github and Heroku. Smooth, beautiful and fast experiences. So reliable.
I miss the old days of Smarty + jQuery UI. That was a better direction.
Had we invested this much effort into that approach, we would've had a much better performing web today.
Thanks for your work, this really looks promising!
One question I keep thinking about. What if I want to still use React on the frontend, does it still make sense to use Phoenix for the backend then or am I throwing all benefits over board then?
reply