Clearly it depends what your use-cae is, but for a large class of apps that you'd build with Django it feels just right for me: http://intercoolerjs.org/2016/10/05/how-it-feels-to-learn-in...
My apologies if you have street cred in the field, but I don't know you, so have no reason to trust your recommendation. Please tell me what makes this particular project better than any alternatives.
The setup is not really straight forward, and generally I have problems mixing django static files in my .scss url() , so this is far from perfect. I'm using it with a main .ts file that requires various components based on the class of body tag, so I can use this in simple reload request use case. Also I've complicated things a little so my webpack bundles are collected as other static files and my static template tag also works.
But yeah, using react in typescript and sass in this way for the frontend has accelerated my development a lot.
the vast majority of websites that need indexing should not need JS to create the html.
the vast majority of web apps that benefit from being SPAs are behind some form of login/auth and so do not need indexing.
yet there's this obsession with writing SPAs that can be pre-rendered for better indexing. i only assume this is a solution to the desire of using nodejs and javascript as a server-side language regardless of merit.
Since the html output is minimal, presumably you require something like python-react that pipes the output through a nodejs server?
Presumably building the same in a React SPA using Django, that would also mean maintaining the routing system in two different frameworks at once?