https://github.com/makeplane/plane this is a fairly big project done in django + next.
Very interesting. It's using django as API backend. Since they are already using nextjs do you know why they chooose django over nodejs for the API backend?
Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
11–19 of 19 posts
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#12Honestly, this doesn’t sound like a bad idea at all! Next.js is great for frontend, and Django is super powerful for backend, especially for AI/ML stuff. The main challenge would be making Django feel as seamless as Node.js does with Next.js, especially with API routes and SSR. But if you can figure out a good DX, it could actually be really useful for AI devs who want a smoother frontend experience without dealing w…
Thanks. Yes those are exactly what I am thinking but you described way better than me! Plus there are so many reactjs template that AI devs could pick up. The difficulty would be how to make the django portion easier for reactjs dev to use and reactjs portion easier for python dev to handle.
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#13Yes, bad idea. It increases complexity and number of moving parts, breaking points without the need for it
Hahaha, I agree. I hope it can be at least better than reactjs + Django (API backend)
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#14Does django + intertia.js solve this usecase already?
Interesting! Have not heard about intertia. Lemme check it out!
Thanks!
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#15Depends, do you know Python, and the ecosystem around django? If not it's probably wiser to stick to javascript. That said, you can accomplish some good things with Django.
Yes true. What if could take advantage of both ecosystm.
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#16Well that's exactly the stack I used for some internal applications in a job I had.
Is a little bit tedious to set everything together, but other than that, is fine.
You most likely will lost some good DX stuff like same types in front and back (like with using tRPC and the like), but in general is pretty good: logic in python, UI in js/ts.
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#17Well that's exactly the stack I used for some internal applications in a job I had. Is a little bit tedious to set everything together, but other than that, is fine. You most likely will lost some good DX stuff like same types in front and back (like with using tRPC and the like), but in general is pretty good: logic in python, UI in js/ts.
Nice! Did you use tRPC to pass server side data from python to javascript?
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#18What about plotly dash since it wraps react anyway?
Re: Is creating a Django backed reactjs (like nextjs but use django) a bad idea?
#19Well that's exactly the stack I used for some internal applications in a job I had. Is a little bit tedious to set everything together, but other than that, is fine. You most likely will lost some good DX stuff like same types in front and back (like with using tRPC and the like), but in general is pretty good: logic in python, UI in js/ts.
Nice! Did you use tRPC to pass server side data from python to javascript?
No, but at the time we were using a monorepo for both backend and frontend, so is feasible to keep an action that checks that the models in the front and the back are aligned on each pull request.