Post #2032973

@zachleat To be clear, I'm not defending React as an alternative where static site generators are an option. I'm talking about it in the context of shared stateful content, i.e. "apps". In this context there's no question of "React or no React", only "React or what else". Several prominent voices in the React space have for years now expressed a desire to move on to "the next thing" when it comes around and it's increasingly looking like that time is near with attitudes towards React shifting the same way they did when people abandoned AngularJS (which had been dominant in the same space at its time, though of course the space itself has been consistently increasing in overall size since 1997). Heck, remember Google's "Object.observe" proposal, which failed so badly they had to redesign Angular2 from scratch? I'm not sure what the point of collecting a thousand ways to say "React bad" is when most of these are presented without the historical context. But if the goal is to get people to abandon React there needs to be a clear direction to move towards. And no, "islands" aren't a panacea unless you just want to ignore apps entirely, aside from them feeling oddly reminiscent of Web2.0 era widgets and could be argued to be the "junk drawer" approach to performance concerns, i.e. simply excluding what you don't want to or can't improve from the relevant metrics.