undefined | Better HN

0 pointsreilly30006y ago0 comments

The next.js PI is beautifully simple. I completely agree with what you’re saying with regard to tradeoffs, but I’ve been remarkably impressed with the simplicity of the NextJS api and it’s clear, concise documentation.

0 comments

3 comments · 1 top-level

Vinnl6y ago· 2 in thread

Working through their docs recently my first thought was: huh, I was under the impression that it would do more for me.

But then I realised that it actually does do a lot for me, but they really managed to package it all up in a relatively (and deceptively) simple API that so far still does not seem leaky at all.

simion3146y ago

Usually the leaky abstraction will appear later, I remember years ago I was implementing a react component and for some reason the focus was lost from an input when an update was happening. So eventually you are forced to understand what is happening and to apply workarounds. I have experienced a number of issues where some bug suddenly appears and until I read the source code of the abstraction I could not fix it(not only JS frameworks).

Vinnl6y ago

Sure, all the usual caveats for React and server- vs. client-side rendering still apply - but those aren't abstracted over.

1 more reply

j / k navigate · click thread line to collapse