#Prioritize NextJS!!

1 messages · Page 1 of 1 (latest)

stone tusk
#

there aren't a lot of alternatives to smth like nextjs for deno as well

bleak lintel
#

personally, i definitely don't think that nextjs is the be-all and end-all when it comes to web frameworks. yes, it has its place, just like so many other web frameworks. in a couple of years (at most) something else will be the "nextjs replacer" framework.

formal pawn
#

Nextjs support is part of npm. I'm agree, full support for npm in deno, and Nextjs support in deno will change the game in js world.
I think npm and Nestjs support should be a priority than adding new feature

stone tusk
#

i'm against full npm support, if you want to use next.js, simply use node.js - why do you need to use a node-native framework with deno?

stone tusk
#

nextjs is not the go-to framework for backend development

#

i have no idea what you're talking about

subtle hare
#

NextJS is not a zero-compromise choice for web projects. Especially with a huge part of the community having a dislike for JSX in the first place. It is just a very popular web framework written around Node. "unlikely for the next 3+ years" when there's a new web framework rolling out every other week?

Also, Deno being a web backend wouldn't even require NextJS support, considering the majority of Node backends run on express and express middleware.

It makes more sense for Deno to concentrate on Fresh (and probably some JSX-free alternatives) at the moment.

stone tusk
#

like nextjs's backend routes are extremely limited in their functionality and in no way a alternative to pure backend frameworks

shut heron
subtle oar
#

What’s the cost of indirection & abstractions? Excess cognitive load!

bleak lintel
subtle hare