You're viewing a single thread.
These things are true if you build a SPA wrong. Believe it or not there are lots of ways to build server side rendered pages wrong too.
76 9 ReplyYeah this meme and the OP have no idea how to build an SPA.
21 14 ReplyI don't know what the hell you're interpreting into this 15-word-meme, but I do. I'm not saying all SPAs are shit, I'm saying far too many are. And "far too many" being more than one that I can think of. Even the Lemmy webpage breaks history caching.
30 3 ReplyI know what an SPA is, but I would be laughing so hard at this thread if I didn’t know what it meant.
“Yeah man. Dude doesn’t know his SPAs!”
Reminds me of that Saturday Night Live skit with the woodworkers comparing everything to working on the lathe.
2 0 Reply
> implying there's a "right way" to build an SPA.
10 14 ReplyThere are a lot of standard practices like… using a router to load the content of your SPA according to the url.
16 3 ReplyWhat I'm saying is, there's no right way to build a thing that is inherently wrong.
8 9 ReplyYou could build it with no input sanitation. That’s wrong.
7 1 ReplyEven 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.
6 11 ReplyI strongly disagree, but I respect your opinion which was no doubt formed by different experiences with web technologies than I’ve had.
16 1 ReplyNot 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.
1 0 ReplyWhat do you mean only runs one stack? Like front end framework? That would be the point. But it can communicate with any backend.
1 0 Reply
There's no one right way. Saying there are wrong ways doesn't imply the existence of one right way, though.
4 0 Reply