Ephera to Programmer [email protected]English • 11 months agoSingle-Page Applicationlemmy.mlimagemessage-square115fedilinkarrow-up1504arrow-down131
arrow-up1473arrow-down1imageSingle-Page Applicationlemmy.mlEphera to Programmer [email protected]English • 11 months agomessage-square115fedilink
minus-square@[email protected]linkfedilink13•11 months agoThere are a lot of standard practices like… using a router to load the content of your SPA according to the url.
minus-square@gruelinkEnglish-1•edit-211 months agoWhat I’m saying is, there’s no right way to build a thing that is inherently wrong.
minus-square@[email protected]linkfedilink6•edit-211 months agoYou could build it with no input sanitation. That’s wrong.
minus-square@gruelinkEnglish-5•11 months agoEven a perfectly-built SPA is a thing that should’ve been a different kind of program (a native app or even something like Java Web Start) instead.
minus-square@[email protected]linkfedilink15•11 months agoI strongly disagree, but I respect your opinion which was no doubt formed by different experiences with web technologies than I’ve had.
minus-square@[email protected]linkfedilink1•11 months agoNot that it’s inherently good or bad, but the heavier web apps get the more a browser represents a sort of virtualization environment that only runs one stack. I think that’s interesting.
minus-square@[email protected]linkfedilink1•11 months agoWhat do you mean only runs one stack? Like front end framework? That would be the point. But it can communicate with any backend.
minus-squareandrewlinkfedilinkEnglish4•11 months agoThere’s no one right way. Saying there are wrong ways doesn’t imply the existence of one right way, though.
> implying there’s a “right way” to build an SPA.
There are a lot of standard practices like… using a router to load the content of your SPA according to the url.
What I’m saying is, there’s no right way to build a thing that is inherently wrong.
You could build it with no input sanitation. That’s wrong.
Even a perfectly-built SPA is a thing that should’ve been a different kind of program (a native app or even something like Java Web Start) instead.
I strongly disagree, but I respect your opinion which was no doubt formed by different experiences with web technologies than I’ve had.
Not that it’s inherently good or bad, but the heavier web apps get the more a browser represents a sort of virtualization environment that only runs one stack. I think that’s interesting.
What do you mean only runs one stack? Like front end framework? That would be the point. But it can communicate with any backend.
There’s no one right way. Saying there are wrong ways doesn’t imply the existence of one right way, though.