React'ing to Why Kent C. Dodds Won't Use Next.js

Dax and Adam read through Kent C. Dodds' article on Why He Won't Use Next.js and give their thoughts on the web platform, independence, Next.js eating React, collaboration, experimenting on users, too much magic, and complexity. Oh and something's off with the X.Want to carry on the conversation? Join us in Discord.Links:Linear – A better way to build productsDax on X: “the rest of us have literally no hope” / XNext.js ConfHow About Tomorrow? | Next.js Conf 2022 RecapWhy I Won’t Use Next.js | Epic Web Dev by Kent C. Doddssolidjs.comIndex - OpenNextScale & Ship Faster with a Composable Web Architecture | NetlifyRemix - Build Better WebsitesRefactoring UICustom fonts without compromise using Next.js and next/font – VercelMooToolsDomainr · fast, free, domain name search, short URLs, new gTLDs, whoisBuy a domain name - Register cheap domain names from $0.99 - NamecheapLive streaming with RiversideTopics discussed: (00:00) - Meeting Trash (00:30) - X feels off (03:28) - Design, easter eggs, and clothing style (08:05) - NextJS Conf is our origin story (10:07) - Why Kent C Dodds Won't Use Next.js (16:41) - Whatever you use is probably fine (19:21) - The web platform (24:10) - Independance (34:10) - NextJS is eating React (36:04) - Collaboration has gone down (40:22) - Experimenting on my users (45:16) - Too much magic (52:45) - Complexity (55:39) - Stability (56:34) - Capabilities (58:05) - Twitter's logo as a unicode character (01:01:40) - Back to the conclusion (01:05:07) - Tech conference fomo (01:08:00) - Is Dax an F1 fan?