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

nickbytes pfp
nickbytes
@nickbytes.eth
Yea it has it's own templating. Templating is probably my least favorite part, and a lot of people just use Django to create a REST API using https://www.django-rest-framework.org/
1 reply
0 recast
1 reaction

MOLO pfp
MOLO
@molo
Feels more like express.js then, which has a lot of features but also a ton of freedom, versus next. Next I wouldn’t use for something backend-heavy
1 reply
0 recast
0 reaction

Gabriel Ayuso pfp
Gabriel Ayuso
@gabrielayuso.eth
I'm new to the modern node frameworks world but Next definitely is pushing more heavily on leveraging server-side rendering.
1 reply
0 recast
0 reaction

MOLO pfp
MOLO
@molo
Yeah they're an FE framework slowly trying to become full stack (also building out DBs, they love showing off their edge stuff). IMO best option that exists in the JS world. And I don't like python so it's defacto best option overall :)
0 reply
0 recast
0 reaction