Next.js is excellent. I'm generally against frameworks and prefer to roll my own... but my latest project is in Next, because the SSR is just SO SLICK.
Nice! Coming from the CanJS community, it's nice to see React finally catching up on this and it's really interesting how similar the end approaches were. I wonder how much the work from DoneJS influenced this
Great talk. Guillermo Rauch, I am interested in implementing my own component gallery ('sketch in the browser') for a new product build. Is the example shown in the talk simply a Next.js page with all the components dropped in?
By progressive web app i'm assuming you're going by this definition: Progressive - Work for every user, regardless of browser choice because they’re built with progressive enhancement as a core tenet. You can deploy a static html site with next.js and have increased performance and readability by different browsers. Refer to the next.js documentation as well as the browser standards you are going to target.
To keep up with JS trends? That's a full-time job. More seriously, I devote most of Monday mornings to catch up via 2 different newsletters, and keep an eye on Twitter every now and then. Most important part is to go down the rabbit hole when you find something interesting; just skimming through the headlines is not enough.
The problem i have had using Next is simply that it is not React. While if find it nice for small apps and marketing pages building large apps brings along headaches when wanting to use mobx or redux, other React libraries such as styled components and the separation of ssr and csr i feel could be made simpler -- such as using existing lifecycle functions. The benifits of optimizations such as code splitting i find negligible in small apps and like i said above large, complicated apps are annoying to maintain if not only because of having to create a serve and handle route mapping there. Also many of the Next Components I find convoluted or unnecessary. Take the next/Link compared to React Routers Link or the entire Document/Head/Body structure compared to ReactHelmet. While I understand that these components are made to help facilitate ssr and csr in a transparent way I find them to be more complicated than needed especially when other parts such as global __NEXT_DATA__ variables provide less transparency. These are just my opinions and dont get me wrong i love using Next especially when i need a few view rendered on an existing backend server without the overhead of setting up react/es6. But for large complicated web/native apps I'm sticking with CreateReactApp/ReactRouter4/MobX
Great respect for Guillermo and Zeit
Next.js is excellent. I'm generally against frameworks and prefer to roll my own... but my latest project is in Next, because the SSR is just SO SLICK.
Aged so well
Nice! Coming from the CanJS community, it's nice to see React finally catching up on this and it's really interesting how similar the end approaches were. I wonder how much the work from DoneJS influenced this
Tom Sieverding lol
UN CRACK! OJALA ALGUN DIA LLEGUE XD
Bien carajo
amazing
Great talk. Guillermo Rauch, I am interested in implementing my own component gallery ('sketch in the browser') for a new product build. Is the example shown in the talk simply a Next.js page with all the components dropped in?
Listeing to the speaker left me very confused what Next.js does exactly and how it can be hepful in developing React apps.
Please check out the intro here: zeit.co/blog/next
I assumed a basic knowledge with it, next time I'll re-iterate it in the beginning!
You should use inline CSS. `styled-jsx` is already integrated: github.com/zeit/styled-jsx
Guillermo can i do a progressive web app with next.js?
By progressive web app i'm assuming you're going by this definition:
Progressive - Work for every user, regardless of browser choice because they’re built with progressive enhancement as a core tenet.
You can deploy a static html site with next.js and have increased performance and readability by different browsers. Refer to the next.js documentation as well as the browser standards you are going to target.
awesome. Please turn on CC
I'm going to ask an odd question. To keep up with these trends, how much personal research do you do per week? An hour, more?
To keep up with JS trends? That's a full-time job. More seriously, I devote most of Monday mornings to catch up via 2 different newsletters, and keep an eye on Twitter every now and then. Most important part is to go down the rabbit hole when you find something interesting; just skimming through the headlines is not enough.
2023)
I can bet people who disliked this video (may be next, may be the shift, may be react itself) once are ashamed and would like to withdraw the vote!
2022
The problem i have had using Next is simply that it is not React. While if find it nice for small apps and marketing pages building large apps brings along headaches when wanting to use mobx or redux, other React libraries such as styled components and the separation of ssr and csr i feel could be made simpler -- such as using existing lifecycle functions. The benifits of optimizations such as code splitting i find negligible in small apps and like i said above large, complicated apps are annoying to maintain if not only because of having to create a serve and handle route mapping there. Also many of the Next Components I find convoluted or unnecessary. Take the next/Link compared to React Routers Link or the entire Document/Head/Body structure compared to ReactHelmet. While I understand that these components are made to help facilitate ssr and csr in a transparent way I find them to be more complicated than needed especially when other parts such as global __NEXT_DATA__ variables provide less transparency. These are just my opinions and dont get me wrong i love using Next especially when i need a few view rendered on an existing backend server without the overhead of setting up react/es6. But for large complicated web/native apps I'm sticking with CreateReactApp/ReactRouter4/MobX
If only time travel were possible, stop Guillermo from getting to the event on time, he never gives his talk and maybe we'd have a sane web today
*can i with console visit blocked facebook profile ? i think i can ;)*
*I need 1 profile visit*