Post

Every single #Nextjs time project I’ve come into, the team has regretted choosing it as the codebase expands. Inevitably, there is some background process or more complex backend logic that needs to happen and the project ends up with disparate code spread between Supabase functions, Lambdas, etc

0 reposts4 likes

Everything is trade offs of course. I’ve worked on multiple #Rails projects, and while the backend and Gems allow very tightly integrated solutions, you then have to fill in many gaps on the front end side. I’m very bullish on bridging these gaps with #Inertiajs