Content pfp
Content
@
0 reply
0 recast
0 reaction

nickbytes pfp
nickbytes
@nickbytes.eth
Javascript still needs its Rails/Django equivalent. Next.js has empowered a bunch of frontend devs to build fullstack applications, but there’s a ton of footguns and the flexibility still has people floundering in problems long-solved by other frameworks.
9 replies
1 recast
3 reactions

MOLO pfp
MOLO
@molo
what are the problems you’re thinking of?
1 reply
0 recast
0 reaction

nickbytes pfp
nickbytes
@nickbytes.eth
This sums up pretty well https://warpcast.com/leewardbound/0xf777db
1 reply
0 recast
1 reaction

MOLO pfp
MOLO
@molo
How do you write frontend with django? Does it have its own templating or can you just hook it into react?
2 replies
0 recast
0 reaction

Leeward Bound pfp
Leeward Bound
@leewardbound
Personally I hate the templating and html and form handling in Django - I use Django as a strict backend layer for API development (formerly Django-rest-framework, now graphene for gql), and I build frontends in Nextjs + react, which are very adept at frontend concerns (SEO, hydration, routing, query loading, etc)
1 reply
0 recast
1 reaction

Leeward Bound pfp
Leeward Bound
@leewardbound
Absolutely cannot vouch strongly enough for the django+gql+react pattern, it feels like cheat codes - all the best backend tools coupled with a strongly typed API, means you get a best-in-class frontend experience with 95% of the full end-to-end typing experience that the "Full-stack JS" crowd boasts about
1 reply
0 recast
1 reaction