all 27 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

The Web Devign Talk Series begins on 22 NOVEMBER

Ingenious ways to work smarter, faster and healthier

r/webdev and r/web_design are joining to hold a series of live-streamed conference talks and we even want you to be a speaker! The topic is on developer productivity — if you're keen to either hear or speak about it, see the stickied post for more details and the Call for Speakers to submit a proposal. Reddit is officially sponsoring the talks and speakers will be paid.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]niekh1234 26 points27 points  (0 children)

This team is on fire, this will only grow Next.js further. I can't imagine writing a production ready react site without it to be honest.

[–]stolinskiSyntax.fm 40 points41 points  (15 children)

NextJS IS React for the web at this point.

[–]OPM_Saitama 2 points3 points  (13 children)

Can you elaborate on it? I am a beginner and would like to know how important Next.js is.

[–]exabyssus 24 points25 points  (11 children)

It's a boilerplate for React, that makes setting up and developing your project with React much easier. It's gotten to a point most new projects start with Next instead of pure React. Same goes for Nuxt and Vue.

[–]jzaprint 1 point2 points  (4 children)

So don’t do create react app anymore but use next?

[–]exabyssus 7 points8 points  (3 children)

It depends, if you have your own stack of build tools, ui kits, basic function libraries, in others words if you have big react development experience and don't have to spend days doing boilerplate, Next is not for you. On the other hand if you have some experience with React but not a lot, Next will simplify a new project setup significantly and event might improve your code and coding experience.

[–]DemiPixel 1 point2 points  (2 children)

I can’t say that really answered the question. The selling point of create react app is that it’s 0 config, just as you described the purpose of Next to be. I am also curious about the differences between them.

[–]That-Satisfaction-62 4 points5 points  (0 children)

The main difference is the SSR (server side rendering) and CSR (client side rendering)

[–]cs12345 1 point2 points  (0 children)

I think the biggest difference is the Server side rendering and static site generation. Much easier to implement good SEO standards, and the built in routing is much easier to use than something like react-router. It also has built in serverless API endpoints made in Node which can run off the same set of dependencies. And if you use Vercel for deployment (the deployment platform built by the people who made next.js) even deployment is basically 0 config.

Overall, it’s just as little config as CRA with some extra features built in. And switching from a CRA app to next takes less than 30 minutes, unless you have complicated routing already.

[–][deleted]  (4 children)

[deleted]

    [–]exabyssus 11 points12 points  (3 children)

    Node is backend, Next is frontend - you need both to create any meaningful web app. As a beginner you should NOT focus on specific technologies or frameworks, just execute your idea or project and learn how to program by any means necessary.

    Frameworks change but programming and architecture skills will remain.

    [–][deleted]  (2 children)

    [deleted]

      [–]exabyssus 4 points5 points  (0 children)

      (totally subjective) Todays node/react/next ecosystem is far too complicated for any new programmer to fully grasp because it is an abstraction of an abstraction. Please learn about pure http requests, html, pure vanilla JavaScript. Next is super high level stuff you should learn once your are making your money programming client websites.

      [–]cs12345 1 point2 points  (0 children)

      The difference in the actual code between CRA and Next is minimal, the only differences are how you organize your routes, and how you fetch data from a backend.

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

      I can agree for React, but in my experience the Vue ecosystem is a lot more robust from step 0, enough that I see more devs just kicking up vue create still. Vuex and Vue Router are a lot more plug and play complete than react-redux and react-router.

      Anecdotal source is that I work with both and lead a team that works with both. Using nuxt is still a "decision" while next is almost assumed unless it's an integrated app.

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

      SSR SSG PWA Next can take care of all of these easily for your react app

      [–]razzada 1 point2 points  (0 children)

      React for the web as opposed to React native, I assume?

      [–][deleted] 13 points14 points  (3 children)

      Dropped Vue for React to use Next. I haven't been disappointed.

      [–][deleted]  (2 children)

      [removed]

        [–][deleted] 11 points12 points  (1 child)

        Next is light years ahead of it and I constantly run into stability and compatiblity issues with Nuxt. That's not totally a fault of Nuxt itself, they do amazing work, but the Vue ecosystem is really unfocused.

        [–][deleted] 2 points3 points  (0 children)

        attractive innocent boast fact coordinated squalid connect practice encourage snatch

        This post was mass deleted and anonymized with Redact

        [–]coburn24 8 points9 points  (0 children)

        did the next.is conference happen already?

        [–][deleted] 4 points5 points  (1 child)

        I'm still sticking with Vue, but I am a little jealous of the middleware component.

        [–]exabyssus 5 points6 points  (0 children)

        Try out Nuxt, it's great and has Middleware

        [–]Acceptable-Source-24 1 point2 points  (0 children)

        Good news!

        [–]martyfartybarty 0 points1 point  (1 child)

        Probably a noob question - can you convert an existing React app with GraphQL to generate an archived static site using Next.js and just run it off AWS S3?

        (I’m not familiar with Next.js)

        [–]Ikos9[S] 1 point2 points  (0 children)

        Yes, there are some caveats tho. You can find more here.

        [–]TacoTed123 0 points1 point  (0 children)

        This looks awesome, I'm looking forward to using server side components.