3 ms·
> "The ability for JS to run both client/server means we can do things with it that are not possible with PHP or other server-only languages, and frameworks lik
by csmpltn 4y ago
> "The ability for JS to run both client/server means we can do things with it that are not possible with PHP or other server-only languages, and frameworks like React are pushing that boundary. Pointing out that JS has these unique opportunities is not even remotely the same as "forgetting" and "rediscovering" SSR."
Can you provide even a single example for something we can do with JS running on both the client and the server, that was otherwise "impossible" (quoting you here), or very difficult, without this capability?
- mypalmike 4y agoSingle codebase for data object definitions, without an extra data definition language and code generation layer. Which leads to things like... data validation logic that is exactly the same on client and server. Same for serialization/ deserialization code.
- chrischen 4y agoDoing "new" stuff and being more performant is really in the domain of the web browser, not in the javascript libraries that run on browser engines. Saying React doesn't enable "new" stuff in that regard isn't really fair because React isn't meant to do that. What React does do is allow for the development of maintainable complex applications such as most major web apps you use including Instagram, Facebook.com, Netflix.com, etc.