Re:Next.js 13
by apozem on Tuesday October 25, 2022 @03:01PM
(#33334778)
I'm quite alright with new tooling every six months when the new thing is orders of magnitude faster. If people want to compete to make my job as a frontend dev easier and faster, that is just fine.
[ Parent
| on HN ]
Ideally we could learn how to make the existing tools better/faster and create software that can evolve rather than re-writing everything from scratch every six months.
I suspect at some point we hit the limit of the language performance. I can't imagine JavaScript beating Rust when both are written well.
Re:Next.js 13
by AlmostAnyone on Tuesday October 25, 2022 @05:06PM
(#33336190)
There was many years before people started trying to replace Webpack.
True but webpack itself had a ton of churn and made practically no effort to maintain backwards compatibility causing a ton of work with each major update.
Re:Next.js 13
by AlmostAnyone on Tuesday October 25, 2022 @06:11PM
(#33336837)
Hmm, I am using it since v2 and I disagree, it was not so bad. I saw a lot of people had overcomplicated configs that could be simplified a lot, I guess those had some problems upgrading... But mine never had much problems (and not just because my needs were simple...), I just removed some options when going to v4 and that's about it.