Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm using exactly this stack for my current personal project - Elixir/Phoenix and Turbolinks.

Sprinkling in either Elm or Vue for the one or two complicated widgets I'm going to need, but I haven't committed to either one yet.



I've settled on Elixir/Phoenix for the backend.

On the front-end I might still experiment, but I think I'll settle for at least a decent chunk of time on this:

1. React + Styled Components (so html/css/js is finally no longer decoupled in a way that just makes no sense) 2. Page.js or something similar for routing, because I've been bitten too often by react-router and like, and the idea that routing is it's own thing makes sense to me. 3. Baobab.js or something similar for state management: basically, A. a single state object with B. a kind of cemtralized action-flow to change this state, and C. listeners of sorts within various components that trigger a re-render (cursors in the case of Baobab). I could go full-on redux, but it doesn't seem, necessary and I kind of relish running into the situation where, as my apps grow, it turns out to be immediately obvious why Redux does what it does.

I'd be very curious to get some feedback on my choices, and/or alternative suggestions. In particular regarding 3.

EDIT: to be clear, this is for full-on SPA's with no kind of crawling/SEO needs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: