redux-eggs VS inertia

We have docs on code splitting reducers and other Redux logic here:

- https://redux.js.org/usage/code-splitting

There have been some different community packages for helping with that process, but some of them seem to have become outdated (only worked with React-Redux v5, etc). I did see a new one at https://github.com/fostyfost/redux-eggs that seemed like it had potential, but I haven't had a chance to try any of them myself.

I also once saw someone play around with the idea of using React's still-not-technically-final Suspense support to help ensure that a lazy-loaded component that relies on a code-split reducer doesn't actually get rendered until that reducer's state is available. Don't have the link handy atm, but if someone wants it ping me and I can go figure out where that was described.

Also, the new RTK "listener" middleware was specifically designed to replace almost all saga usages, and you can dynamically add more listeners at runtime via dispatch an `addListener()` action:

- https://redux-toolkit.js.org/api/createListenerMiddleware

- https://blog.isquaredsoftware.com/2022/05/presentations-evol...

I did see a recent package called https://github.com/fostyfost/redux-eggs which looked like it did the same kind of "add and remove modular chunks of Redux code" use case, but I haven't had time to try it out.

Inertia.js

This feels a lot like https://inertiajs.com/ which I've really been enjoying using recently

But here's the thing - the more niche your tech stack gets, the less reliable AI becomes. Take my setup for example: I use Elixir, Phoenix, React, and Inertia for my side projects. The Inertia adapter for Phoenix is super new and not widely adopted yet (which is a shame - this combo is incredibly productive and performant). There's just no way current AI models have enough training data on this specific stack to generate useful code. The more specialized your tools, the more you'll need to rely on your own expertise rather than AI assistance.

Inertia.js Official Documentation - Core concepts and API reference

But if I still want to write a React App and keep all that knowledge hard earnt, blood sweat and toil I can as Laravel can do that also with a 'glue' code called Inertia of which I have not played with nearly enough in 2024 and will no doubt explore more in the coming year. Where as I would have reached for Firebase or similar to give me a solid back-end for my front end apps in the React space I can now lean heavily on Inertia to do the heavy lifting for me to integrate with Laravel on the back end, removing lock in to BaaS services and allowing me to 'take back control' of my data, truly owning it on my own cloud VM, swarm, k8s cluster or whatever I like.

I’ve recently been re-building an admin panel in a personal Laravel-based project, convering it from “traditional” Blade views to an Inertia-based solution. As part of this, I’ve been identifying repeating elements that can be extracted into reusable Vue components.

Laravel: Offers SSR capabilities through Inertia.js or its own Livewire component.

Someone managed to fix this issue with a ref hook, https://github.com/inertiajs/inertia/issues/1631#issuecommen...