Programming

17488 readers

110 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 [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

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

submitted 1 year ago by [email protected] to c/programming

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

[–] [email protected] 29 points 1 year ago (1 children)

I think it's more a case of the tool being used, not because it's the best tool for the job, but because it's the tool the dev knows how to use. SSR allows frontend devs to become full-stack devs.

[–] lightsecond 16 points 1 year ago

That’s exactly how we got Javascript on the backend in the first place. I remember when this was the new “weird” thing.