3 ms·
It is far less productive for complex anything, not just UIs. The only way to do home-spun stuff in JS/TS is to narrow the use-cases and components down religi
by tinthedev 2y ago
It is far less productive for complex anything, not just UIs.
The only way to do home-spun stuff in JS/TS is to narrow the use-cases and components down religiously. The moment you'll require more than 2-3 bits of the website to interconnect... take one long hard look at the future and avoid the headache of writing your own JS boilerplate.
I love eschewing JS frameworks as much as the next man, but I also love my free time. Too much to waste it debugging problems coming from hundreds of different user stories and approaches. React's mature enough, as are most of the big libraries commonly leveraged on it.
- winrid 2y agoI don't waste time doing that. Sounds like a skill issue :) React is on like version 18, you guys can keep getting paid to upgrade frontend libraries every year, I'll watch.
- meiraleal 2y ago> React's mature enough, as are most of the big libraries commonly leveraged on it. Mature software doesn't break things every other year.