Hacker News new | ask | show | jobs
by OutsmartDan 1099 days ago
The new docs are extremely annoying; if you're still running a legacy app, sometimes you get put into a doc for a feature you think exists, but then you realize it's not for the right version you're running.

Also the new app routers are very confusing. There are concepts of a layout, template, page, etc. While it's nice to have server rendering at this level, it's difficult to understand what is bubbling which direction, and when to use a layout vs a template. Sometimes after building something one way (eg using layout), you realize you actually need to build it using the other in order for specific features to work.

Old Next was great and simple- new Next has become increasingly frustrating and not so easy to adopt.

3 comments

Apps using the Pages Router aren't legacy, it's totally fine and encouraged to continue using it. We'll continue to support in far into the future and also be adding some new features there, too.

Where are you landing into the docs from, Google? We try to add version history notes at the bottom of docs pages, but maybe we should place these at the top. Open to feedback.

Just keep the old version's docs and have a version select drop down.

I don't want to trawl through what is essentially a changelog, I want to browse/search the docs for the version I am using.

Pressing command+k, attempting to find a solution to an issue- but the solution is for app routes not pages route.

Having them separate was better for documentation satisfaction.

This new routing approach with fetching data everywhere will end up like old PHP mess and then they will discover controllers again :)

I’ve tried to make it work for SPA development but it doesn’t work in that scenario well as all recent data fetching libs were using hooks which you can’t use in async functions. Seem like people aren’t sure how to best solve it now.

It's crazy to me that their docs aren't versioned. Almost forces you to be constantly upgrading to the bleeding edge.