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

Next.js 8 released

nextjs.org

Post reply on HN
Print view View original

1–10 of 118 posts

Re: Next.js 8 released

#3

Post by jypepin »

I've been using Next.js for a fairly big e-commerce project for a client, and I have to say it's great.

The framework itself makes working with a React, universal rendering app much easier than other solutions I've worked with. It's doing a great job at starting very small while at the same time extending for your needs is pretty easy for most things (such as build configs, custom server, etc).

The community is growing and very helpful too.

I'm very glad to see it continue to move so fast and definitely already see it as a very strong option and probably becoming the de-facto solution for JS apps, just how Rails or Django are to Ruby and Python.

Thanks to the team for the great work :)

edit: typos

Re: Next.js 8 released

#4

Post by chimen »

jypepin wrote: post #3

I've been using Next.js for a fairly big e-commerce project for a client, and I have to say it's great. The framework itself makes working with a React, universal rendering app much easier than other solutions I've worked with. It's doing a great job at starting very small while at the same time extending for your needs is pretty easy for most things (such as build configs, custom server, etc). The community is growi…

It's great but not becoming the de-facto. I believe Gatsby is on that path, in terms of popularity they seem to be ahead.

Re: Next.js 8 released

#5

Post by skrebbel »

chimen wrote: post #4
jypepin wrote: post #3

I've been using Next.js for a fairly big e-commerce project for a client, and I have to say it's great. The framework itself makes working with a React, universal rendering app much easier than other solutions I've worked with. It's doing a great job at starting very small while at the same time extending for your needs is pretty easy for most things (such as build configs, custom server, etc). The community is growi…

It's great but not becoming the de-facto. I believe Gatsby is on that path, in terms of popularity they seem to be ahead.

I thought Gatsby is a static site generator?

Re: Next.js 8 released

#6

Post by toper-centage »

skrebbel wrote: post #5
chimen wrote: post #4

Earlier quoted context omitted.

It's great but not becoming the de-facto. I believe Gatsby is on that path, in terms of popularity they seem to be ahead.

I thought Gatsby is a static site generator?

Yes and in that sense it overlaps next a bit... But next is much more.

Re: Next.js 8 released

#7

Post by onion2k »

skrebbel wrote: post #5
chimen wrote: post #4

Earlier quoted context omitted.

It's great but not becoming the de-facto. I believe Gatsby is on that path, in terms of popularity they seem to be ahead.

I thought Gatsby is a static site generator?

It is, but "static site" is just a methodology for delivering content to the browser (static rendered HTML + server side [rendering|hydration] + client side routing). Traditionally people have used static sites for marketing, blogs and documentation but there's no reason why they have to be limited to just those sorts of sites. GatsbyJS's site has tutorials for how you can do authenticated users, ecommerce, etc with it. https://www.gatsbyjs.org/docs/authentication-tutorial/

Re: Next.js 8 released

#8

Post by [deleted] »

jypepin wrote: post #3

I've been using Next.js for a fairly big e-commerce project for a client, and I have to say it's great. The framework itself makes working with a React, universal rendering app much easier than other solutions I've worked with. It's doing a great job at starting very small while at the same time extending for your needs is pretty easy for most things (such as build configs, custom server, etc). The community is growi…

[deleted]

Re: Next.js 8 released

#9

Post by martpie »

Next.js is an awesome framework, but dynamic routing is still a mess, and clean URL masking [0] is unnecessary complicated: you have to add a route handler to Express.js, and you have to use 2 different props to your components to make it work.

The Next team explains it because they don't want to solve this problem by shipping a definition of all the route of the app [1] because it does not scale. But while it is true, it makes dynamic routes extremely painful to use. Hopefully it will be fixed soon.

Another thing not mentioned in the blog post is they started to rewrite the core of Next.js in TypeScript too, which is a big move!

  [0] https://nextjs.org/learn/basics/clean-urls-with-route-masking
  [1] https://github.com/zeit/next.js/issues/4989#issuecomment-442024894

Re: Next.js 8 released

#10

Post by jypepin »

chimen wrote: post #4
jypepin wrote: post #3

I've been using Next.js for a fairly big e-commerce project for a client, and I have to say it's great. The framework itself makes working with a React, universal rendering app much easier than other solutions I've worked with. It's doing a great job at starting very small while at the same time extending for your needs is pretty easy for most things (such as build configs, custom server, etc). The community is growi…

It's great but not becoming the de-facto. I believe Gatsby is on that path, in terms of popularity they seem to be ahead.

Great answer from Tim [1], the lead maintainer of Next on the difference of the 2 (the whole thread is great).

I've never used Gatsby so I can't really judge, but my understanding has always been that Gatsby is mostly focused on static sites. It can definitely do dynamic apps but it being not focused on this would concern me for support / experience of more complex things.

[1] https://www.reddit.com/r/reactjs/comments/992n2r/next_vs_gat...

Post reply on HN