Live data from Hacker News

Next.js 8 released

nextjs.org

101–110 of 118 posts

Re: Next.js 8 released

#101
post #83

Earlier quoted context omitted.

I’m very involved in this space. The company I work for wrote a library similar to Next.js before it was announced and before create-react-app. There are so many things that these solutions solve to only focus on SSR is missing the point. SSR is one benefit of many and others have already explained why they care about that. There are many use cases where both SEO and complex interactions make sense on the same page.…

> Next.js is also going to help you with [...] routing I respect your experience and knowledge but people in this thread say exactly the opposite: Next.js' routing is actually not helping you.

Fair enough. It helps you but it could be better. Depends if you need dynamic routing or not. Personally I don’t find their solution for dynamic routing terrible but it could be better.

Re: Next.js 8 released

#102
post #87
post #84

Earlier quoted context omitted.

> they are only adding static types. The parent says something different and if it were just about adding types then you need just to add a file to DefinitelyTyped which I guess happened already.

Yes it says they are "rewriting the core in TypeScript", but that does not necessarily mean changing the code in any meaningful way. It means adding static types to the core itself, not only the interface (which DefinitivelyTyped is for).

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. No public APIs are changed. Furthermore, we have an extensive test suite of end-to-end tests for both development and production behavior.

Re: Next.js 8 released

#103

Earlier quoted context omitted.

Why they require login for tutorial pages in the first place?

The copy says it's some interactive thing with quizzes and such.

I didn't get any value out of the 'gamification' element. Would have preferred to have not logged in.

Re: Next.js 8 released

#104
post #81

So the tutorial requires me to login with github? Sorry, not gonna happen.

This is great comment and while Zeit/Next.js related folks are happy to explain in this thread why Next is so great, they're not give us any reason why we need to login for a random tutorial. Maybe it's to generate leads? Leads which can be converted to paying customers? This why this whole thing shouldn't be on HN, this thing is conflicted from the ground and driven by commercial interests.

Yo, you wanna chillout with flinging the accusations? Every single one of your comments in this whole thread is either bullheaded negative or a subtle suggestion that Next.js is some marketing conspiracy without its own merit.

If you don't like Next or don't see its usefulness thats fine, but 30,000 stars on Github and pretty varied list[1] of companies seems to suggest that some people do find it useful.

I am not affiliated with Zeit or Next.js in any particular way. Just a happy user of Next and appreciative of all the hard work put into it.

[1] https://nextjs.org/showcase/

Re: Next.js 8 released

#105
post #96

Interesting read from Dec 2018 [1] about Next.js: SSR throughput of your server is significantly less than CSR throughput. For react in particular, the throughput impact is extremely large. ReactDOMServer.renderToString is a synchronous CPU bound call, which holds the event loop, which means the server will not be able to process any other request till ReactDOMServer.renderToString completes. [...] Using Pre-Rendered…

Acronym translations:

   SSR: Server-side rendering
   CSR: Client-side rendering
   CRA: create-react-app

Re: Next.js 8 released

#106
post #86
post #9

Next.js is an awesome framework, but dynamic routing is still a mess, and clean URL masking [0] is unnecessary complicated: you have to add a route handler to Express.js, and you have to use 2 different props to your components to make it work. The Next team explains it because they don't want to solve this problem by shipping a definition of all the route of the app [1] because it does not scale. But while it is tru…

Hey there! Not sure if you've seen this guide here, but there is a way to setup dynamic routing with clean URLs that doesn't require adding your own server handler if you use Now v2 for deployments: https://zeit.co/guides/custom-next-js-server-to-routes/ Also, I recently wrote about how I locally develop Now v2 apps with an example of SSR dynamic routes: https://medium.com/digital-surgeons-engineering/how-to-set-u...

Is this Now only as I'm sure most of us don't use Now?

Re: Next.js 8 released

#107
post #86

Earlier quoted context omitted.

Hey there! Not sure if you've seen this guide here, but there is a way to setup dynamic routing with clean URLs that doesn't require adding your own server handler if you use Now v2 for deployments: https://zeit.co/guides/custom-next-js-server-to-routes/ Also, I recently wrote about how I locally develop Now v2 apps with an example of SSR dynamic routes: https://medium.com/digital-surgeons-engineering/how-to-set-u...

Is this Now only as I'm sure most of us don't use Now?

Yeah Now only

Re: Next.js 8 released

#108
post #103

Earlier quoted context omitted.

The copy says it's some interactive thing with quizzes and such.

I didn't get any value out of the 'gamification' element. Would have preferred to have not logged in.

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 all, this is mostly for historical reasons. The original learnnextjs.com built by Arunoda was based on another project he created for teaching Meteor.

Anyway as said we're rewriting /learn, using MDX (http://github.com/mdx-js/mdx) for content and the quizzes will store the result in your browser.

Re: Next.js 8 released

#109
post #103

Earlier quoted context omitted.

I didn't get any value out of the 'gamification' element. Would have preferred to have not logged in.

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 all, this is mostly for historical reasons. The original learnnextjs.com built by Arunoda was based on another project he created for teaching Meteor. Anyway as said we're rewriting /learn,…

Very cool! Makes sense that you got it for free from Meteor, great that you're iterating based on feedback.

Re: Next.js 8 released

#110
post #88

Earlier quoted context omitted.

Can you share what you found limiting with nuxtjs routing? Genuinely curious.

As you probably know, Nuxt.js uses a folder to url mapping, so say /src/views/contact/index.vue maps to /contact In my case I wanted to be able to change the url depending on the language of the user. And not by prefixing it with a /en/contact vs /de/kontact. To make matters more complicated, I serve multiple domains from the same node/express instance and determine the correct site data to render based on the domain…

You can use custom routing and its actually recommended for bigger projects you can check it here if you want https://vuejsdevelopers.com/2018/07/16/7-tips-large-nuxt-app...
Post reply on HN