I DONT USE NEXT JS

ThePrimeTime・2 minutes read

The text discusses a debate between Kent C. Dodds and Lee Rob regarding the React frameworks Next.js and Remix, emphasizing the importance of choosing a modern framework to stay marketable and productive. The author recommends Remix over Next.js for its focus on solving web development issues, full-stack capabilities, and better user experience, highlighting the importance of skill mastery over tool choice.

Insights

The debate between Kent C. Dodds and Lee Rob highlights the importance of choosing a modern framework like Remix or Next.js for developers to enhance productivity and marketability, emphasizing the significance of skill mastery over the tool itself.
Remix stands out for its focus on solving web application development challenges, offering full-stack capabilities similar to Next.js, and prioritizing stability and reduced API footprint, contrasting with Next.js's perceived complexity and magic, ultimately providing a better user experience with less code.

Get key ideas from YouTube videos. It’s free

Recent questions

What are the key differences between Remix and Next.js?
Remix focuses on solving web app issues for better user experience.
How does Remix approach deployment compared to Next.js?
Remix allows deployment anywhere for JavaScript, emphasizing standards.
What are the concerns regarding Next.js marketing experimental features?
Concerns arise over Next.js marketing experimental features as stable.
How does Remix prioritize stability in comparison to Next.js?
Remix team prioritizes stability with a slow approach to version updates.
How does Next.js aim to provide self-hosting features for developers?
Next.js aims to provide self-hosting features for control and freedom.

Related videos

Summary

00:00

Choosing Modern Frameworks: Remix vs Next.js

The text discusses a debate between Kent C. Dodds and Lee Rob regarding React and frameworks like Next.js and Remix.
It highlights the need for developers to choose a modern framework for projects, whether new or existing, to stay marketable and productive.
The author has been using Remix since its release in 2020 and recommends it for its full-stack capabilities similar to Next.js.
Remix is favored over Next.js due to its focus on solving web application development issues and providing a better user experience.
The author emphasizes the importance of skill over tool choice, stating that proficiency with a tool is more crucial than the tool itself.
Testing Library's approach of exposing platform APIs directly is praised for its transferability and ease of integration with other tools.
Remix is compared to Enzyme in terms of API exposure, with Remix offering direct access to request headers and cookies.
The text discusses the challenges of deploying Next.js outside of Vercel, leading to the creation of Open Next.js for AWS Lambda support.
Hosting Next.js as a regular Node.js application is described as a significant challenge, with differing opinions on the ease of deployment.
The profitability and pricing strategies of Vercel are questioned, suggesting potential issues for users if Vercel's offerings become problematic.

13:09

"Next.js and Remix: Stability vs. Revenue"

Engineers make money with every request, raising concerns about overreliance on this model.
Remix allows deployment anywhere for JavaScript, emphasizing standards.
Versell's hiring of React team members has affected collaboration within the team.
Confusion arises between React and Next.js, especially regarding server components.
Next.js aims to be synonymous with React, potentially increasing revenue.
Concerns arise over Next.js marketing experimental features as stable.
Next.js overrides global fetch function for automatic caching, raising red flags for some.
Next.js complexity and magic are criticized, with concerns about the impact on the web platform.
Remix team prioritizes stability, with a slow approach to version updates.
Stability and reduced API footprint are valued by the Remix team, contrasting with perceived complexity in Next.js.

26:22

Comparing React Router, Remix, and Next.js Frameworks

React Router has historically had issues with breaking where state should have been, impacting apps built with it.
Remix has been a preferable alternative due to its stability and lack of major upgrade challenges.
The comparison between Next.js and Remix emphasizes that both frameworks are capable of building great projects.
Remix is seen as having a wider pit of success compared to Next.js, aligning better with software maintainability.
The user experience with Remix has been noted to be better with less code compared to Next.js.
Next.js has updated to use the app router, which is considered stable but relies on Canary features.
The evolution of Next.js has introduced middleware based on web request, response, and fetch, aligning with standardized web APIs.
Next.js 13 introduced a new foundation with the app router, emphasizing the importance of web standard APIs.
Route handlers in Next.js allow for creating arbitrary API endpoints, utilizing web APIs directly for headers, cookies, and more.
The importance of embracing web APIs in new frameworks like Remix, Next.js, and others is highlighted for better development practices.

39:30

"Next.js: Self-hosting and Seamless Development"

Openex exists due to the difficulty of deploying Next.js, leading to a focus on self-hosting improvements.
Next start is utilized by major companies like Walmart, TikTok, and Starbucks to self-host Next.js.
Next.js aims to provide self-hosting features for developers seeking control and freedom.
Versell funds Next.js, aligning incentives for maintaining and building default deployment outputs.
Next.js has over 85,000 monthly active developers expecting prompt bug fixes and feature releases.
Hosting Next.js as a node application is perceived as challenging by some developers.
Versell's pricing and infrastructure can impact users' decisions to use their services.
Next.js and React teams collaborate closely on framework development, emphasizing compatibility and stability.
The App Router in Next.js introduces a new model distinct from the Pages Router, requiring incremental adoption.
Next.js offers a seamless development experience, eliminating the need for separate backends and infrastructure concerns.

52:34

HDMX: Server-Client Separation with Specialized Languages

HDMX is favored for its ability to separate server and client roles, with the server as the source of truth and the client as a responsive element. While acknowledging the benefits of tools like Next.js and Remix for client-side interactivity, the preference lies in investing in languages specialized for specific tasks, such as JavaScript for DOM manipulation, Go for server operations, and Rust for server tasks. The speaker expresses a continued preference for HDMX due to its alignment with this approach, despite acknowledging the impressive features of Next.js and Remix.

Try it yourself — It’s free.