2 ms·
> But the unique power of web components (in the browser) is that they can render before JavaScript. React components cannot do this — full stop. Umm, that's w
by ivanjermakov 3y ago
> But the unique power of web components (in the browser) is that they can render before JavaScript. React components cannot do this — full stop.
Umm, that's why SSR was created?
- willio58 3y agoWeb components are standardized by the web consortium. They are the way web browsers have agreed components should work. They have value inherently and don’t necessarily mean you can’t use react, in fact they can be used together very well especially for things like framework agnostic design systems. Basically, web components have more holding power inherently because they are browser native. React and SSR is just a great way to augment that. While I write react daily and love it, I think it’s important to realize no methodology today will have any real importance or meaning 100 years from now. It’s all a means to an end and frameworks and web components are just different means. In 2123, people will glance at a paragraph about react and move on to the next topic in programming history.
- ivanjermakov 3y agoSSR is the traditional way to write frontends. PHP, Rails, JSP, most technologies that revolutionized the web were rendering HTML on the server. SSR, in one form or another, will exist for as long as HTML will. Additionally, SSR doesn't replace web components, it's a different technology with an intersecting feature. There is no problem to use them together.
- iteratethis 3y agoWhich is React SSR. A few years down the line, React is gone. Legacy. Most on this forum don't care, they'll just move to another project.