Hacker News Reader

It's because React (and other SPA technologies that also happen to work with SSR) is all the buzz. It doesn't actually necessarily make sense. The risk to a project is usually NOT the technology chosen for frontend.

Django templates are perfectly fine as long as you leverage template tags the way they were intended.

View on HN

I would agree that "Django templates are perfectly fine"... until: https://www.reactivated.io/documentation/philosophy-goals/#u...

Of course there's many ways around this, but doing them in a declarative, type-safe way is not trivial when using Django templates.

Given that example, would you say using SSR with React to add bits of dynamic-ness is directly comparable with using templates + hotwire/htmx?

Or is it an apples to oranges comparison?

It's very similar, except hotwire/htmx won't give you server rendering. It's not that big a deal if it's just small snippets.

This does make testing a lot easier, as the server response is identical to the hydrated client.

A hypertext approach such as HTMX in fact does give you server rendering, since you send to the client a normal SSR page with some extra annotations that add SPA features.

For React, SSR is secondary. For HTMX, it is primary.

There's a lot of good advice in that article. I liked the part on cookies in particular. You rarely read that anywhere.

Reply on news.ycombinator.com