3 ms·
He's not wrong, but he willing-fully ignores stuff he doesn't like, including much of the JS eco-system. I semi-liked him at some point, but his video on the T
by authorfly 2y ago
He's not wrong, but he willing-fully ignores stuff he doesn't like, including much of the JS eco-system.
I semi-liked him at some point, but his video on the T3 stack lost my support. In a few videos he completely ignored that Next.js and other stacks already had shipped the features T3 supposedly uniquely had. T3 is different to work with, in my opinion worse, and he completely ignores the innovation from Next.js that had already happened since the Next.js code he compares it to. It's like he launched a 1995 model car in 2000 and started comparing it to all the 1990s cars.
I know if Next.js hadn't innovated, his framework would have stood a chance at wider immediate adoption. It had some real, and unique pros. Unfortunately, by the time of his release, his ideas and knowledge were either already outdated, or he is hiding the truth from himself. A lot of the supposed benefit of T3 stack is now provided in Next.js by default.
The man should look at usage stats. He's getting more pithy and angry over time. I don't think it's wise.