Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why we ditched Next.js and never looked back

northflank.com

Post reply on HN
Print view View original

11–16 of 16 posts

Re: Why we ditched Next.js and never looked back

#11

Post by koakuma-chan »

aurareturn wrote: post #3

I'm unconvinced. Basic page renders were taking 200-400ms. I've never seen this. Next.js is very fast for basic pages. If a Google crawler or our Ahrefs SEO monitoring tool hit multiple pages at once, the site would start crashing multiple times per week. This just seems like code issue and not Next.js. Plenty of sites use Next.js and have billions of views/year. Large pages, especially ones with dynamic content, cou…

I used Next.js with mui.com at one point, and after each change in dev mode it took 10s to recompile. I don’t touch anything that has to do with Vercel ever since then.

Re: Why we ditched Next.js and never looked back

#12

Post by kylehotchkiss »

koakuma-chan wrote: post #11
aurareturn wrote: post #3

I'm unconvinced. Basic page renders were taking 200-400ms. I've never seen this. Next.js is very fast for basic pages. If a Google crawler or our Ahrefs SEO monitoring tool hit multiple pages at once, the site would start crashing multiple times per week. This just seems like code issue and not Next.js. Plenty of sites use Next.js and have billions of views/year. Large pages, especially ones with dynamic content, cou…

I used Next.js with mui.com at one point, and after each change in dev mode it took 10s to recompile. I don’t touch anything that has to do with Vercel ever since then.

That sounds like a MUI problem, not a next problem. What a clunky UI framework. Next plus tailwind remains lightning fast for me.

Re: Why we ditched Next.js and never looked back

#13

Post by theogravity »

koakuma-chan wrote: post #11
aurareturn wrote: post #3

I'm unconvinced. Basic page renders were taking 200-400ms. I've never seen this. Next.js is very fast for basic pages. If a Google crawler or our Ahrefs SEO monitoring tool hit multiple pages at once, the site would start crashing multiple times per week. This just seems like code issue and not Next.js. Plenty of sites use Next.js and have billions of views/year. Large pages, especially ones with dynamic content, cou…

I used Next.js with mui.com at one point, and after each change in dev mode it took 10s to recompile. I don’t touch anything that has to do with Vercel ever since then.

Next.js doesn't play well with barrel packages (large packages that export everything into the main entrypoint file). It's a known issue (but rarely mentioned when you read about working with Next.js):

https://github.com/vercel/next.js/issues/48748

I've never used MUI, but assuming that MUI is a barrel package, and you do the following:

  import { Component } from "mui";
Next.js ends up compiling the entire package instead of just that component you need. If MUI has their components exported into separate files, an optimization would be:

  import { Component } from "mui/path/to/component";

Re: Why we ditched Next.js and never looked back

#14

Post by koakuma-chan »

theogravity wrote: post #13
koakuma-chan wrote: post #11

Earlier quoted context omitted.

I used Next.js with mui.com at one point, and after each change in dev mode it took 10s to recompile. I don’t touch anything that has to do with Vercel ever since then.

Next.js doesn't play well with barrel packages (large packages that export everything into the main entrypoint file). It's a known issue (but rarely mentioned when you read about working with Next.js): https://github.com/vercel/next.js/issues/48748 I've never used MUI, but assuming that MUI is a barrel package, and you do the following: import { Component } from "mui"; Next.js ends up compiling the entire package ins…

I switched to Astro plus tailwind and never looked back. If you are interested though, imports are a pretty big thing in mui https://mui.com/material-ui/guides/minimizing-bundle-size/.

Re: Why we ditched Next.js and never looked back

#15

Post by aurareturn »

koakuma-chan wrote: post #14
theogravity wrote: post #13

Earlier quoted context omitted.

Next.js doesn't play well with barrel packages (large packages that export everything into the main entrypoint file). It's a known issue (but rarely mentioned when you read about working with Next.js): https://github.com/vercel/next.js/issues/48748 I've never used MUI, but assuming that MUI is a barrel package, and you do the following: import { Component } from "mui"; Next.js ends up compiling the entire package ins…

I switched to Astro plus tailwind and never looked back. If you are interested though, imports are a pretty big thing in mui https://mui.com/material-ui/guides/minimizing-bundle-size/ .

To be honest, if you're making a content site such as a marketing site or blog, it really doesn't matter what you use. You can use Next, Astro, Gastby, HTML/CSS etc. Doesn't matter.

Next.js excels when you have a complex app with interactions, SSR requirements, CSR requirements, backend requirements, etc.

Re: Why we ditched Next.js and never looked back

#16

Post by koakuma-chan »

aurareturn wrote: post #15
koakuma-chan wrote: post #14

Earlier quoted context omitted.

I switched to Astro plus tailwind and never looked back. If you are interested though, imports are a pretty big thing in mui https://mui.com/material-ui/guides/minimizing-bundle-size/ .

To be honest, if you're making a content site such as a marketing site or blog, it really doesn't matter what you use. You can use Next, Astro, Gastby, HTML/CSS etc. Doesn't matter. Next.js excels when you have a complex app with interactions, SSR requirements, CSR requirements, backend requirements, etc.

I disagree. I’m building an audio player in Astro.

https://github.com/mayo-dayo/app

Post reply on HN