Next.js is a framework to get pretty excited about as it's offering:
- Zero setup with the ability to use the filesystem as an API
- Auto-magic server rendering and code splitting - whoa!
- Allowing developers to explicitly define data fetching effects
- Baked-in performance optimization, and
- Easy-peasy deployments ala their Now platform
Get back some dev time, reinvest in product
Having worked on a mission-critical, end-to-end digital product at Tesla, these are all things that we have needed to create ourselves, or address in one form or another, for our specific needs. This is fine and typical in most teams, which I don't suspect is an effort that is going away all-together, but to have a stable and supported framework like Zeit's Next.js that has a lot of common developer needs baked-in with the ability to customize the setup further is huge!
There's huge potential to save engineers lots of time upfront that can then be used to focus on building specific features and enhancements for their company's product(s). I also see cross-functional teammates, like release and devops engineers, benefiting from some of the initial leg work being done upfront that they can customize to fit their own build pipeline needs.
And, with Next.js being built with automatic server-side rendering and code splitting, the end-user of a team's digital product is bound to benefit greatly; for instance, experiencing faster page load times and time-to-interaction with the product/web app.
So, looking forward to how Next.js evolves, and exploring use cases for it both at work and on personal projects.
Zeit Vercel team!
I am a problem solver: a tech and people leader with a passion and proven track-record in building and leading empathetic, productive teams—remote and on-site—within a continuous learning culture, while championing usable, inclusive digital products and online experiences. I am also a father, advisor, life-long learner, advocate, community builder, and speaker—I am Human. Learn more