3 ms·

Sort of, but not always. My blog at https://www.silviogutierrez.com https://www.silviogutierrez.com is React+Django strictly server side. I like JSX that much.

Sort of, but not always. My blog at https://www.silviogutierrez.com https://www.silviogutierrez.com is React+Django strictly server side. I like JSX that much. Try loading it with JS disabled. Same at my business site: https://www.joyapp.com https://www.joyapp.com. It was a huge ordeal getting it setup (with React SSR, etc), but it's definitely doable. I've open sourced it but it sorely needs documentation (incoming): https://github.com/silviogutierrez/reactivated https://github.com/silviogutierrez/reactivated Basically, despite the tooling (not because of it), once you get going with JSX, TypeScript and the like, nothing else comes close. At least in my experience. But again, none of the above stops me from dumping that output into a single cache key per request. It's still dynamic, just cached robustly.

dopeboy 6y ago
I'm a fellow django + react developer. What are your thoughts around moving to Next.js?
- silviogutierrez 6y ago
  In my opinion: nothing, and I do mean nothing, comes close to the productivity of Django + Forms + FormSets + Admin. I've tried everything under the sun[1] The model->form and presentation layer is so intuitive and robust that I'm surprised no JS framework has rebuilt it. Too much is focused around REST instead of domain specific inputs / outputs.[2] So yea, I've focused on making Django more React-friendly. I want to stick to it. [1] Ok, maybe Rails comes close. [2] https://news.ycombinator.com/item?id=21875331 https://news.ycombinator.com/item?id=21875331