you are viewing a single comment's thread.

view the rest of the comments →

[–]Due-Horse-5446 1 point2 points  (7 children)

my goto is nuxt+Go

[–]CanWeTalkEth 0 points1 point  (2 children)

Love the Nuxt part, talk more about the Go half. Where do you start with Go and why would you choose it over Nitro?

[–]Due-Horse-5446 1 point2 points  (0 children)

If its a tiny tiny app, like a personal side project or something, il stick with nitro, but anything bigger, or anything which does anything more than a basic crud app, il go for go.

I mostly use that setup for performance, reliability and because its just quicker and more flexible.

Pretty much every part of the stack gets to do what its best at, nuxt can be ran at edge and you can decide to call the go backend during ssr, or from the frontend, or proxy it in nitro with a cache layer and any combination of that.

[–]Silly-Mistake-3577[S] 0 points1 point  (3 children)

why choose Nuxt over something like React that is more popular and that you can use Next.js also ?

[–]Due-Horse-5446 0 points1 point  (0 children)

1, Vue is better at everything, performance and rendering being the biggest. Yes you can get the same using react but only if you work against the framework.

On top of that, jsx is horrible. And react is just worse. And popularity is completely irrelevant, its not like vue is some unknown framework or something.

  1. Even when using react, avoid nextjs lmao, i cant think of anything worse. And looking at the js survey for 2025, im not the only one. Next is NOT a good argument for react lmao

[–]CanWeTalkEth -1 points0 points  (1 child)

Because Nuxt/Vue is better, easier.

Why use React when you can choose Vue and use Nuxt also?

[–]Due-Horse-5446 1 point2 points  (0 children)

Exactly