🔗 Using Phoenix with React and Inertia | Dimitrios Lytras

I love React. I've worked with various people and companies, and I've seen its power in action. I've also seen some of the worst things done with it, but fixing those buys "Little Dutch" toys for my daughter, so I have no complaints there.

Jokes aside, React has a massive ecosystem and, most importantly, known unknowns. It's considered boring technology now (at least the SPA parts), and the problem you might have has already been tackled and documented somewhere.

My pain point has always been the back-end of things in JavaScript. Next.js is utterly unreliable for reasons I won't expand on here, and everything else (Remix/RR, TanStack) doesn't have opinions on trivial stuff I don't want to configure. On the other hand, frameworks like Rails and Laravel have great solutions but use languages I don't enjoy that much. So, Phoenix strikes the perfect balance.

To put these two frameworks together without having to ship two separate applications, I use Inertia.