Regarding the error handling, just return response and show the error. For example if trying to load a dashboard and you get a 403, just display an error.
40 karma · joined October 29, 2023
Regarding the error handling, just return response and show the error. For example if trying to load a dashboard and you get a 403, just display an error.
What's even weirder is that they could copy the structure from dozens of other frameworks, some of which are nearly 20 years old now, which have solved pretty much every possible problem already.
But no, just throw views,data, io, auth checks etc. everywhere and hope it builds.
Especially next community seems to be full of people who don't seem to know anything about web development complaining because they don't know how cookies work or something...
You can still use react , vue, solid or whatever for the dynamic parts that make sense to do clientside
But noone wants to pay.
I tried nextjs and for a simple site with few pages and echo endpoint it creates like 2MB of javascript. I could make the same result in 100 lines of code but apparently it's not fast or modern.
The issue is that static file hosting and effective servers don't generate money for infra providers. So better run some js cluster** to get a login form for client.