Reorx’s Forge 头像

消息来源频道

Reorx’s Forge

@reorx_share

频道3,130 位成员公开可见0 人在线

A chronicle of my journey in forging my ideas into writings and products. Archive: https://app.shokichan.com/c/tg/reorx_share

成员规模3,130 位成员
在线情况0 人在线
消息总数6,041 条消息
浏览量总数784,746 次浏览

在这个频道里搜索消息……

t.me/reorx_share

喷 Next App Router
https://github.com/vercel/next.js/issues/43704#issuecomment-1920413060
Next used to uphold the conventions typically seen in server-side frameworks. However, when it began to "upgrade" (or "downgrade," based on my personal experience) to App Router, it became more insular. This wouldn't be problematic if the newly introduced concepts meshed well with the existing ones. However, the reality is that App Router doesn't match the capabilities of Pages Router, nor is it comparable to other server-side frameworks like Django, Rails, or Laravel from a completeness perspective. If you've used any of the frameworks I mentioned, you'd likely find that tasks that are straightforward in those often become difficult or impossible in Next.
App Router seems to be best suited for those new to writing server-side code. It's not even ideal for those who only have experience with Pages Router. I'd wager that no one who has had to migrate from an existing Pages Router project — one substantial enough to be used in a business scenario — is satisfied with the experience in App Router.