this post was submitted on 03 Feb 2024
478 points (94.3% liked)
Programmer Humor
32398 readers
621 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Yeah this meme and the OP have no idea how to build an SPA.
I 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.
I 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.
> 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.