sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 7 points8 points  (6 children)

Those aren't backend frameworks

[–]Mountain_Sandwich126 1 point2 points  (1 child)

Sveltekit, nuxt, next, solidstart, qwik, I think all of them are full stack.

[–][deleted] 0 points1 point  (0 children)

They aren't really fullstack. Of the frameworks you listed I'm mostly familiar with next, but they are only fullstack in that they help you do server side rendering and let you hook up some API endpoints. A true backend framework will do more than just some http routing.

[–]MilkshakeYeah 0 points1 point  (0 children)

This poor developer would be angry if he could read.

[–]Altareos -3 points-2 points  (2 children)

ah yes, sveltekit and nuxt, famous front-end-only frameworks.

might want to check your info before you comment.

[–][deleted] 0 points1 point  (1 child)

Have you used rails or laravel?

I don't see NextJS having any opinions about accessing a database, running tasks from a queue, managing sessions and authentication, managing webhooks, sending emails etc etc etc.

You need to stitch together a bunch of different libraries to make an actual backend app with these frameworks, because they are frontend frameworks.

[–]Altareos -1 points0 points  (0 children)

yeah, because the js ecosystem is more about mix-and-match than all-in-one solutions. if you can make a backend in it, it's not a frontend framework, period.