timneutkens

8 ms·

1.
by timneutkens 7y ago
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 upgrading.
2.
by timneutkens 7y ago
> 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 changes for quite some time and have been
3.
Next.js 8.0.4(nextjs.org)
3 points by timneutkens 7y ago|0 comments
4.
by timneutkens 8y ago
> 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 WIP pull-request: https://github
5.
by timneutkens 8y ago
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 above)
6.
by timneutkens 8y ago
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 worlds. Just to explain the reason there is a login at
7.
by timneutkens 8y ago
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 files over one by one. N
8.
by timneutkens 8y ago
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 Serverless you're able to scale the renderer to infinite instan
9.
by timneutkens 8y ago
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, but are very trivial to add.
10.
by timneutkens 8y ago
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 project was actually co-created by several other people
11.
by timneutkens 8y ago
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/micro, which is a very lightweight way to build APIs.
12.
by timneutkens 8y ago
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 infrastructure at ZEIT (e.g..: Naoyuki Kanezawa led all the initial rele
13.
by timneutkens 8y ago
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 server. We do have an example for it: https:/&#x2
14.
by timneutkens 9y ago
https://medium.com/@timneutkens/introducing-valet-blazing-fa...
15.
Show HN: Introducing Valet+, Blazing fast PHP development environment(github.com)
4 points by timneutkens 9y ago|1 comments
16.
Show HN: Introducing Valet+, Blazing fast PHP development environment(medium.com)
3 points by timneutkens 9y ago|1 comments
17.
Micro 8: Better for Production, Easier for Development(zeit.co)
4 points by timneutkens 9y ago|0 comments
18.
by timneutkens 10y ago
We're on it, thanks!