April 28th, 2020

Replying to a tweet from @scottjehl

If you mean server-side rendering+rehydration, please say server-side rendering+rehydration.

The problems don’t come from the server-side rendering part; they come from the rehydration.

51° N , 0° E

Also on Twitter

Reply Retweet Favourite

Responses

Scott Jehl

I agree, but I was under the impression that the term’s common usage assumed that. There’s static generated, and there’s SSR.

# Posted by Scott Jehl on Tuesday, April 28th, 2020 at 3:31pm

Dave Rupert

This is where I land on the issue too. There’s a few kinds of client render strategies [client-only, rehydration, progressive enhancement] but maybe only two server render strategies [static + dynamic (from database)]

Matthew Phillips

The term was essentially created to describe the process of taking a client framework and running in a server environment to produce an HTML string. I don’t recall the term ever being used in the ~20 years before frameworks started doing that.

Andrew Mottaz

I have been using ‘SSR’ with the same assumption. Realizing now its not great, because if someone said ‘Server-side rendering’ I would assume any solution that vends fully-baked html fits. I guess I’ve always used SSR with ‘Angular SSR’ or ‘React SSR’ as explicit or implied.

Scott Jehl

I agree. From others though, I usually hear SSR used to describe a step you add to improve an otherwise thick-client setup, where delivery was nothing but “hydration” of an empty div. I think that’s because frameworks initially adopted SSR to fix their rendering, not resilience

# Posted by Scott Jehl on Tuesday, April 28th, 2020 at 3:48pm

Scott Jehl

I strictly agree, while practically disagreeing. I’d side with your usage if I had a choice. In practice I see the term used differently though, to refer to a framework performance mitigation pattern. Adopted for SEO & perceived performance, but not always resilient for usability

# Posted by Scott Jehl on Tuesday, April 28th, 2020 at 3:52pm

Scott Jehl

I’d even say “rendering” is an odd server term for generating static HTML anyway, and the frameworks can have it. 😁

# Posted by Scott Jehl on Tuesday, April 28th, 2020 at 3:55pm

Scott Jehl

It’s a good question. I don’t recall ever calling server-side work “rendering” before client frameworks needed a way to output code on the server. Server “generated”, “templated”, “server-side”… etc. All those were common.

# Posted by Scott Jehl on Tuesday, April 28th, 2020 at 3:58pm

1 Share

# Shared by André Jaenisch on Tuesday, April 28th, 2020 at 5:05pm

6 Likes

# Liked by Alex Morris on Tuesday, April 28th, 2020 at 4:07pm

# Liked by Scott Jehl on Tuesday, April 28th, 2020 at 4:07pm

# Liked by Micah Godbolt on Tuesday, April 28th, 2020 at 4:07pm

# Liked by Dave Rupert on Tuesday, April 28th, 2020 at 4:08pm

# Liked by André Jaenisch on Tuesday, April 28th, 2020 at 5:09pm

# Liked by Ben Seven on Tuesday, April 28th, 2020 at 11:01pm

Have you published a response to this? :