4 ms·

> Stack: Next.js, React, TailwindCSS, shadcn/ui, four languages (EN/DE/FR/JA). The AI picked most of this when I said "modern and clean." I’m not an AI hater b

> Stack: Next.js, React, TailwindCSS, shadcn/ui, four languages (EN/DE/FR/JA). The AI picked most of this when I said "modern and clean." I’m not an AI hater but I do see this as evidence of LLMs being susceptible to chasing trends as much as people. Next.js with server rendered React is not a stack that an experienced web developer would have recommended for a “clean” solution to a collection of financial calculators. It’s the answer you’d get if you asked for the stack that’s trending the most lately.

aenis 9mo ago
Could be, but that stack happens to also solve for a lot of problems totally unexperienced people will struggle with (such as, to not look too far, CORS issues). Good reco for a non-tech person to build a frontend. And besides, who cares which stack is used as long as its used. Its not like this will ever be maintained. If anything, if a need for a new feature emerges 5 months down the road the whole thing can be re-done from scratch in one sitting without writing a single line of code.
TiredOfLife 9mo ago
Next.js is 9 years, React 12 years old.
zeroxfe 9mo ago
TBH, that's pretty much the stack I'd pick if I were building anything new by hand. If you look at the site, there's a lot going on and Next + React + Tailwind does not seem so crazy. These are all quite reliable well-understood components, and far from "chasing trends" IMO.
fantasizr 9mo ago
vibe coding so far has really homogenized the tech stacks by the self promoters. Vercel is printing money off this phenomenon that's a self fulfilling snowball. But stack diversity is good, not everything needs to be js/ts
dysoco 9mo ago
> Next.js with server rendered React is not a stack that an experienced web developer would have recommended for a “clean” solution to a collection of financial calculators Do you speak with web developers on a daily basis? It seems to be the default stack for everyone to build from from a Saas to a TODO app for the last 5 years or so.

aenis 9mo ago

Could be, but that stack happens to also solve for a lot of problems totally unexperienced people will struggle with (such as, to not look too far, CORS issues). Good reco for a non-tech person to build a frontend. And besides, who cares which stack is used as long as its used. Its not like this will ever be maintained. If anything, if a need for a new feature emerges 5 months down the road the whole thing can be re-done from scratch in one sitting without writing a single line of code.

TiredOfLife 9mo ago

Next.js is 9 years, React 12 years old.

zeroxfe 9mo ago

TBH, that's pretty much the stack I'd pick if I were building anything new by hand. If you look at the site, there's a lot going on and Next + React + Tailwind does not seem so crazy. These are all quite reliable well-understood components, and far from "chasing trends" IMO.

fantasizr 9mo ago

vibe coding so far has really homogenized the tech stacks by the self promoters. Vercel is printing money off this phenomenon that's a self fulfilling snowball. But stack diversity is good, not everything needs to be js/ts

dysoco 9mo ago

> Next.js with server rendered React is not a stack that an experienced web developer would have recommended for a “clean” solution to a collection of financial calculators Do you speak with web developers on a daily basis? It seems to be the default stack for everyone to build from from a Saas to a TODO app for the last 5 years or so.