Programming

17378 readers

582 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Why is React, a client side rendering framework, a popular choice for server side rendering? (lemmy.ml)

submitted 1 year ago by cyclohexane@lemmy.ml to c/programming@programming.dev

32 comments fedilink hide all child comments

React (and Vue, et al) was built with client side rendering in mind. It just does not seem to fit the server side rendering pattern.

What are the use cases? From my perspective, if your app is a rich web app with a lot of interactivity, you probably want CSR and don't benefit much from SSR.

If you have a content-centric site, or a site with some interactivity but not much, you want a static site generator, or SSR. But in that case, a template engine with some smaller client side libraries (jQuery or AlpineJS or idk what all is out there).

Using React SSR for all of these seems like the wrong tool. What am I missing?

you are viewing a single comment's thread
view the rest of the comments

[–] lysdexic@programming.dev 3 points 1 year ago* (last edited 1 year ago) (1 children)

Is it not generating HTML on the server to be served to the client?

No, it generates the code that creates the DOM, sets the application state based on the user's setting, and updates the webapp to resume working in a consistent state.

It basically sends a frozen instance of a full blown JavaScript application.

What you’re describing is, in my opinion, an overly complicated form of dynamically rendering HTML on the backend.

That's because you're oblivious to the problem domain,and thus you're falling back to the unrelated but similar sounding things you're familiar with to fill in the void of your understanding of the actual problem.

Anyway, that’s my opinion on the matter

My point is that your opinion is a misinformed one,and really doesn't hold up to scrutiny.

[–] foo@withachanceof.com 1 points 1 year ago

Alright, I'm not going to get into an internet pissing contest over front end techniques since despite being in the industry for over a decade I've been deemed oblivious and misinformed based on two comments. I'll keep doing things my way and you can do it your way. I'm not going to lose sleep over it or resort to calling names over a comment on the internet of someone's opinion I don't agree with.