Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are the downsides/risks in comparison to traditional SSR? #13

Closed
robhrt7 opened this issue Apr 17, 2017 · 1 comment
Closed

What are the downsides/risks in comparison to traditional SSR? #13

robhrt7 opened this issue Apr 17, 2017 · 1 comment

Comments

@robhrt7
Copy link

robhrt7 commented Apr 17, 2017

Hi,

First of all, I'm very impressed with the results we got during the tests of the library. You did really a great job here!

But as we all know, such huge performance gains usually come at a cost, so I wonder, which kind of risks and limitations this SSR solution implies comparing to ReactDOMServer.renderToStaticMarkup?

I've also noticed in some of the issues, that you mentioned you're using it in production at Yandex, is it still the case?

Cheers

@alt-j
Copy link
Owner

alt-j commented May 2, 2017

The biggest trouble you can encounter using our rendering instead of native is the re-rendering that occurs when the application is initialized on the client. Details here.

@alt-j alt-j closed this as completed May 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants