[trojans1290]

Thanks for the breakdown on the above.

I’m wondering - have you ever tried a batteries included backend framework + react? So maybe ror, Django, laravel, spring boot, etc? At what point is it too much racking on various node packages vs just using a proven backend framework + openapi? Then run wild with react on the frontend.

[Escapado]

I bought into the end 2 end typesafety + everything is written in TypeScript hype and it did allow us to build a large portion of our application fairly quickly. Again, it's the 90% that work great this way and I don't think other batteries included frameworks would have saved us. I would also say that complexity in our case leans more on the frontend so having a more batteries included backend would not have been that helpful.

What I will say though is that if I could go back I would probably reconsider the "everything in typescript" and "lets use nextjs, it's what everybody uses" and reach for something more performant because the things that turned out to be difficult to build cleanly again existed on the edges of all of this.

Perhaps Go or Rust for the backend, generate a client or bindings and Solid or Svelte for the frontend.

[trojans1290]

Could you share some of the edges you can into? Agreed that seems the hip move now is to go all in on ts without looking at alternatives.