Today, I did some maintenance work on a Next.js course website (we have tons of them built on Next.js), and I thought to myself:<\/p>\n\n\n\n
\n“Wow, this framework has been around for a long time and continues to evolve. It is certainly not a one-hit-wonder.”<\/p>\n<\/blockquote>\n\n\n\n
For context, I’m generally more of a purist, opting to use vanilla JavaScript and building on the web platform in most situations. Even so, I wanted to acknowledge my respect for the framework and those who have worked hard to develop and evolve Next.js (and, more broadly, React). It is certainly giving us new ways to think about building web apps.<\/p>\n\n\n\n
Next.js wasn’t always the king.<\/h2>\n\n\n\n
To new folks in the industry: Next.js wasn’t always on top. For instance, I remember when Gatsby was constantly in the news as one of the first significant meta frameworks built on React. It was the first framework to build static sites with JSX on the front and back end. As folks hit limits in the framework and pushed against its edges, it could not come up with solutions and eventually fell out of favor.<\/p>\n\n\n\n
Today, Astro<\/a> is filling that gap of static sites. But if you want a complete application development ecosystem on this paradigm, Next.js is currently it.<\/p>\n\n\n\n
Frontend Masters has been teaching Next.js since 2020.<\/h2>\n\n\n\n
Next.js has been building for years \u2013 our first course on Next.js<\/a> was released back in 2020. Our Node.js teacher, Scott Moss, loved the framework and convinced us to continue releasing course updates as the Next.js evolved. After the framework released App router and server actions, Scott returned to teach v3 of the Intro to Next.js course<\/a>.<\/p>\n\n\n\n
It takes a lot<\/em> to remain in the hearts of developers for years.<\/strong> <\/h2>\n\n\n\n
Remaining in the zeitgeist is always impressive to see. <\/strong>And even more-so now, when everyone is focused on where the framework is going to do Next (see what I did there).<\/p>\n\n\n\n
Drawing the boundaries thinner between infrastructure, the server, and, ultimately, the client is a daunting task. Even if it’s not the best approach for every problem, it pushes the boundaries of what’s possible through an approach that respects interactivity as a first-class citizen. <\/p>\n\n\n\n
Note that when I say Next is not the best approach for everything, that’s more so because of Node.js as a platform. Frontend Masters is built on Go, which we think fits our needs best for our given set of challenges. These ideas of putting interactivity first will eventually make their way into other frameworks and platforms as time passes.<\/p>\n\n\n\n
We are excited by the new ideas emerging from the React\/Next.js community!<\/h2>\n\n\n\n
At Frontend Masters, we have built a lot on Next.js: course websites, full-stack projects, and courses. We will continue to release courses on lower levels of the stack and welcome the ideas that Next.js is bringing to our web developer ecosystem!<\/p>\n\n\n\n
Whatever happens from here, I wanted to write this little piece to give my respect and ensure folks in the community. We want developers to build the best apps possible and their dream careers. And if that’s increasingly on Next.js, we’ll be here for it, doing our best to teach the framework and everything underneath it (JavaScript, TypeScript, React, Browser APIs, etc).<\/p>\n\n\n\n
\u270c\ufe0f<\/p>\n","protected":false},"excerpt":{"rendered":"
Today, I did some maintenance work on a Next.js course website (we have tons of them built on Next.js), and I thought to myself: “Wow, this framework has been around for a long time and continues to evolve. It is certainly not a one-hit-wonder.” For context, I’m generally more of a purist, opting to use […]<\/p>\n","protected":false},"author":2,"featured_media":982,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"sig_custom_text":"","sig_image_type":"featured-image","sig_custom_image":0,"sig_is_disabled":false,"inline_featured_image":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[109],"class_list":["post-871","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-post","tag-next-js"],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/frontendmasters.com\/blog\/wp-content\/uploads\/2024\/02\/twitter-card.png?fit=2800%2C1600&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/871","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/comments?post=871"}],"version-history":[{"count":57,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/871\/revisions"}],"predecessor-version":[{"id":987,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/871\/revisions\/987"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/media\/982"}],"wp:attachment":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/media?parent=871"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/categories?post=871"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/tags?post=871"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}