UI only reacts to the responses from backend. Of course it has some amount of logic not to show things user doesn't have permission to do anyway.
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.
While Remix seems a bit more reasonable than some other js frameworks, they all share the same problem: fundamental architecture.
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.
I don't think issues are a good measurement for popular repos. Majority of them are just basic skill issues and inability to read 2 pages of docs.
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...
It's just nonsensical to use a device that dictates what you can install on it. Well, Androids don't come with root permissions either ( you should be able to get it easily if you want imo ) but at least you can install any app, even just create your own.
Good thing about htmx style solutions is that it's easy to implement the features you need without extra bs. Often it's so much simpler and cleaner to code something than using a generalized library or framework.
You can still use react , vue, solid or whatever for the dynamic parts that make sense to do clientside
They could just show dumb ads and it might even work better. It's not so hard, you look at the page /content and get the ad category. I've had Google and Meta account for more than 10 years and all ads are completely irrelevant. I go to r/programming on new browser and they show me ads that actually might have something interesting.
never had an issue with YouTube. At least until now they only try to block blockers if you are signed in. And there really is no reason to login to watch videos.
Why make it complicated? The language supports catching errors, use that. You may not like it but that's the thing you have. Of course you can wrap errors, return [response,error] or whatever in your implementation of api calls etc. but you don't need third-party libraries for that.
The amount of complexity they add with all combinations or render modes, caches and abstraction layers is incredible. For most webapps you can just ship html or create SPA and it's fast enough. If shipping 30kB of js on first load is an issue, then send plain html.
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.
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.