Sven Slootweg (soft-deprecated) @joepie91@pixie.town

@alinanorakari If you wanted to give an example, then you should've probably actually taken a few minutes to understand its context.

Had you done so, you would have learned that a) this being an extremely time-sensitive disclosure, development speed was *literally* the most important priority, unlike in most projects, b) the check would have been impossible without browser-side code, and c) everything *except for* that check works fine without JS!

I wasn't "defending" anything. I was trying to help you by providing resources that you could pass on to people to save yourself time explaining how to do server-side templating. What I linked isn't "more like" what you're endorsing, it literally *is* what you're endorsing, for a specific tech stack. It was meant to support the point of "don't needlessly do browser-side JS".

What *I* don't appreciate is people lashing out at me when I'm trying to help them, based on broad (and wrong) generalizations like "oh it says React, so it must be unnecessary complex", without even bothering to understand what is actually being suggested.

@alinanorakari This is beginning to smell an awful lot like a personal attack rather than a good-faith conversation.

@alinanorakari @forever@fedi.nullob.si @arcade Like, to clarify: express-react-views runs on the *server* side, and functions like any other server-side templating library would

@alinanorakari @forever@fedi.nullob.si @arcade I'm not sure what you're trying to argue here... the first link isn't about React at all (it specifically uses a 'dedicated' server-side templating library), and the latter literally *is* a templating library that just happens to use JSX. I feel like you're assuming a certain complexity associated with 'React' that isn't actually there... React itself is pretty much just a data-to-HTML converter, just like any other templater really.

@alinanorakari @forever@fedi.nullob.si @arcade Huh? This is specifically about server-side rendering of templates, as an alternative to browser-side SPAs.

@alinanorakari @forever@fedi.nullob.si @arcade Possibly useful to keep in your back pocket for when talking to someone who is doing React and Node:
- https://gist.github.com/joepie91/c0069ab0e0da40cc7b54b8c2203befe1
- https://www.npmjs.com/package/@joepie91/express-react-views

@alinanorakari @arcade @forever@fedi.nullob.si Ah yeah the 'unnecessary SPAs' are definitely an issue. I've been trying to tell people to stop doing that forever, but it's hard to fight against the SPA hype...

@alinanorakari @arcade @forever@fedi.nullob.si It's often all the tracker/thirdparty bullshit responsible for that tbh - not just analytics, but also A/B testing platforms, support widgets, ads, etc. The world would be so much better off without that shit

@arcade @forever@fedi.nullob.si Honestly React isn't even the problem here, it's that "progressive enhancement" has completely fallen out of the collective consciousness among web developers. It's entirely possible to do progressive enhancement with React when you actually care about it! It's not even particularly hard...