Viewing profile — timneutkens

We're very committed to introducing only the necessary changes and features. On top of that we have an extensive integration test suite to ensure no features are broken when upgrad…

> There are features/patterns in Next.js that made sense 6 months / a year ago but are now not preferred Do you have an example of what changed? We haven't really made any breaking…

> great that you're iterating based on feedback Thank you for providing feedback in a friendly way, we're always happy to improve where possible! In case you're curious we have a W…

Great explanation @mAritz! Thank you for your feedback @Ndymium, we've shipped a new version of the website that has a loading indication (based on the with-loading example posted …

We're currently working on rewriting /learn to not require any login while still retaining the gamification element (in offline storage). Meaning that you get the best of both worl…

Max is definitely right here. We're not planning to deprecate or "completely rewrite" anything. We're not even "rewriting everything in Typescript at once". We're slowly converting…

It actually works really well for render workloads like server-side rendering too, the reason for this is that rendering can be quite expensive and blocks the thread. With Serverle…

By default Next.js scores 100/100 on performance and best practices eg https://nextjs-3q3i4heaj.now.sh/ (SEO / Accessibility are not 100 as I didn't add meta tags in this example, …

I'm going to post the same answer I gave in another thread on the initial post: As said elsewhere, I mostly act as a curator of a very large effort of hundreds of individuals. The …

Next.js is not prescriptive about your backend stack, it gives you a way to fetch data using `getInitialProps`. At ZEIT most of our APIs are built using Micro: github.com/zeit/micr…

As said elsewhere, I mostly act as a curator of a very large effort of hundreds of individuals. The project was actually co-created by several other people who work on infrastructu…

create-react-app is actually removing this feature in an upcoming release. We don't have plans to include it as a feature to Next.js as you can already implement it using a custom …

https://medium.com/@timneutkens/introducing-valet-blazing-fa...

We're on it, thanks!