(no title)
__oh_es | 1 year ago
I think there are two main issues with js stacks - react and too much plumbing.
React based frameworks require too much thought about lifecycles and management & synchronisation of client state. RSCs could make this easier, but I think the whole use server/use client is a mistake and pushes the problem onto third party frameworks which aren’t focused enough to close off some doors, in the fear they loose marketshare. Remix and redwood may be on the right track but lets see in the next few months.
Plumbing is an issue because you still end up creating a somewhat separate api that feeds into your components. That wiring sucks time and adds to the maintenance workload.
Adonisjs with htmx and tsx templates feel like they’re the right direction but as another post pointed out, adonis doesn’t quite feel like js.
I think the solution is more magic and conventions like RoR provides. I think more opinion is good here - the wild west needed some law.
0xblinq|1 year ago
Also, react has nothing to do with all of this. This is about backend.
Laravel is a great example of this kind of framework, and with inertia you can use react in a sensible way.
And also, htmx is no way the solution to anything g of this. It’s only useful for the minimal examples, you can build anything slightly advanced with it without everything becoming a mess.
__oh_es|1 year ago
Mind elaborating on why react has nothing to do with this?
I appreciate your comment on htmx - I have yet to work with it on a larger scale.