> if your content can only be rendered by a user-agent with full JavaScript support, your content isn't a fully formed citizen of the Web. I actually agree, in

> if your content can only be rendered by a user-agent with full JavaScript support, your content isn't a fully formed citizen of the Web. I actually agree, in a sense, but without the pejorativeness that I infer from your comment. The web apps that are reasonable to build in Angular/React/etc. without server-side rendering support are not traditional hypertext documents that would be archived by IA, indexed by a search engine, or viewed from Lynx. These are things like GMail or complex interactive dashboards (e.g. CRMs). In that sense they're not "fully formed citizens of the Web," if you believe that only traditional hypertext documents satisfy that requirement. There are types of web sites that are a hybrid of the two, like a NYT or Medium article that is mostly text but also contains some interactive data visualizations. Those interactive components can reasonable be built in React or similar, and I don't see that as a problem, since you inherently need JavaScript to use those anyway, plus search engines will have no trouble indexing the text on the page. At the end of the day though, tooling ought to be good enough to allow server-side rendering for UAs without JavaScript support.