Convince me that backend component frameworks are not pure AIDS. Just write a separate API and SPA it ain't that hard or just server side html if your use case is simple enough.
>>108692641I am writing some software in blazor maui hybrid. so I'm getting a desktop webapp, and an ios and android app in one. Actually pretty nice compared to react aids
IMMA CHARGIN MAH BLAZOR
>>108692671Never used that variant of blazor but using traditional blazor server to develop mobile websites or apps sounds like a bad idea because every page interaction will trigger a synchronous network roundtrip.
>>108692641They are pure aids though.Just use React and keep frontend/backend separate.Only version of blazor worth a damn is blazor wasm, rest is trash.
>>108692856vue > react
>>108692896I hear nothing but good things about vue.Im just happy to have thrown our angularjs frontend in the trash and got to use something new (React).
Personally, I'm writing a Next.js application just as an SSR layer over my separate backend, to pre-build my HTML so that when the page is cached in my infrastructure, it loads fast from the cache without needing SPA. Fuckhuge Javascript packages being pushed to the client, that's for real-time-updating applications, which just isn't my use case.I get to have the modular fractal factory-game development experience of React with the smooth classic user experience of HTML, just because Next.js is rendering the components into HTML before it pushes the text/html response gets to the cache & the client. API routes are for other technologies, I just want fast page loads & fast development without all the browser bloat. In my experience, whenever a page has a mysterious memory leak, it's always using one of those frontend frameworks. HTML really is superior, it just takes longer to write and can become a bitch to manage when you're dreaming up something big. I'd write in exclusively HTML, had I all the time in the world.The real sad reality is industry relevance, though. So many people are hiring for Next.js, and The Great Vibe Code Cleanup Project opens to a lot more Next.js work than HTML work.
>>108692641I use asp net webforms
>>108693072If time to first page load matters just split the js into chunks with an spa. For memory leaks those are usually because of poorly coded react apps which is mostly poopjeets and 3rd party contractors writing garbage code. Also memory leaks aren't limited to react apps it's just that they put the burden of the leaks and other performance problems in the client not the server.
>>108693085It's like blazor but complete dogshit. if it's not just "to maintain a webapp written in 2010" and new dev work, it's completely retarded. Plus it REQUIRES to be hosted on IIS where you can just shove blazor in a docker container
>>108693085I've worked on a legacy app written in this that was abandoned and restarted development several times since about 2014. Razor forms combined with massive inline snippets of JavaScript. Was a complete and utterly slow and bloated mess.
>>108692641We already went through this with shit like PHP, JSP, Razor and webforms. dunno why it made a resurgence
>>108692641>SPAI hope you die in your sleep.
>>108692641I don't even know what any of this shit is. I just use svelte to make a UI then write a stand alone backend. seems like all these big security breach is always come from the gray area in the middle.
>>108692641>Just write a separate API and SPAThis.Our backend is node, our frontend uses vite and gets compiled to static files. We have a little script that generates a bit of frontend code based on the backend, so we can have type checking for API calls and that kind of thing. Aside from that, they're completely separate. Works really well and just takes a few more hours to set up initially.
>>108692641
This generation of webdevs is rrtarded and there's no saving them. Use Rails and ERB templates or whatever other framework that does the same kind of SSR. 99% chance your shutty webapp doesn't need to be an SPA. The only time you need an SPA is when you have something like Google Maps or Figma, but then you wouldn't use React or Nextjs or any other shitty framework either, because you would literally have to write it from scratch. Anything that renders HTML with js, requires a build step and contains HTML or some weird ass XML-like tags inside JS files is crap and is completely unnecessary.
>>108692641Just use web assembly nigga.
>>108692641Before LLMs server rendering was better for caching and search optomisation, not it's just training data for AI
>>108695043Blazor webassembly does not seem to bad but then it is also just a worse version of react/typescript worse tooling.>>108695081All major search engines can render spas. For simple blog/content websites use static generated html you don't need a framework. Nextjs server components and ssr are dumb seem to have gotten popular only because vercel pushed them heavily around the time llms came out. They got very lucky because suddenly there was a mass influx of newfags needing to host nextjs apps with complex backends. Most of these vibe coded apps could have just had a standard spa and a simple sqlite+js backend and you can host it dirt cheap on cloud flare without needing an expensive and complex nextjs backend.
>>108692641I don't even know what they are trying to solve, but those are retarded solutions to a non problem.
>>108695350>I don't even know what they are trying to solveI haven't worked much with nextjs but my experience with blazor server is that lousy backend devs like it because it allows them to build ab unmaintainable barely working frontend tightly coupled to the backend via spaghetti code without needing to create a proper API layer.
>>108695374Anon, server side rendering is never the correct solution.
>>108694594This is THE ONLY sensible post so far in this garbage word vomit filled thread. Django is my tool of choice but genuinely any backend with HTML templating is ALL you need.
>>108694291>our backend is nodeSo you’re a bunch of retards?
>>108692641I am not going to. NEXT is the most retarded shit ever. Literally is the most confusing thing to debug and decipher. Wish the JS bros would just admit that they are toy lang fags and learn a real fucking lang
