Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js 10.2

nextjs.org

Post reply on HN
Print view View original

41–50 of 61 posts

Re: Next.js 10.2

#41

Post by jmacd »

hijklmno wrote: post #14

What turns me off about NextJS is its "opt-out" telemetry. You have to do a bit of magic at the system level "npx next telemetry disable" to turn it off (which you can only figure out by an internet search). This seems very disingenuous on part of Vercel. Make it an "opt-in" or don't fricking track. Conduct a yearly survey or use some other means if you are so interested in improving the framework. I am open to other…

I hope users of OSS can get over this sentiment. With decent and anonymized telemetry data maintainers can make better decisions that benefit the majority of users. Without it, it is the loudest users who get the most attention.

There are major OSS projects with no telemetry that are hamstrung by their lack of insight about which platforms and systems their software is running on.

Everyone should have the right to turn it off, but I think this is going to become the norm.

Re: Next.js 10.2

#42

Post by leerob »

oliverjudge wrote: post #17

Sort of Next related, but I was looking into these frameworks today and it seems all of the easy hosting services jump from free to $20 for what seems to be elaborate static hosting. Is there a middle ground for hobbyists that are running commercial software without spinning up your own VPS (Vercel doesn't look kindly on commercial on their free plan).

You can deploy Next.js anywhere that runs a Node.js server through `next start`. Further, we're recently updated the documentation to include Docker deployment instructions. Hope this helps!

https://nextjs.org/docs/deployment#docker-image

Re: Next.js 10.2

#43

Post by _odey »

westoque wrote: post #33
martpie wrote: post #19

Earlier quoted context omitted.

Counter-opinion here: I am the maintainer of one of the most popular plugin for Next.js, and I am cruelly lacking data about how the users of my plugin use it, that would allow me to choose better defaults for it. I don't have access to the Next.js telemetry data, but I could definitely need to ask the Next.js team from time to time: "so, are your users more using Yarn workspaces? Or npm link? Or something else?", et…

It's not really about the user spying though, it's about the decision of making the user default of "yes, please track my usage so you can make your product better". I would rather have you ask the question first even though I mostly say yes, but transparency is key here.

I agree with this, just ask for consent, it's that simple.

Also, about removing features based on telemetry, of course people are going to disable or block data collection and you will make decisions based on incomplete data. If you must remove something, do it because it makes sense and it fits within your vision for the future of the project you maintain.

Re: Next.js 10.2

#44

Post by ilumanty »

leerob wrote: post #2

Lee from Vercel here. Happy to answer any questions :) If you have any suggestions for how we can improve Next.js, let me know!

next/image has been terribly slow to generate optimized images since 10.0.7.

This issue is a blocker for several people, including myself, and there hasn't been any team response on GitHub yet: https://github.com/vercel/next.js/issues/23637

Re: Next.js 10.2

#45

Post by Dma54rhs »

martpie wrote: post #19
hijklmno wrote: post #14

What turns me off about NextJS is its "opt-out" telemetry. You have to do a bit of magic at the system level "npx next telemetry disable" to turn it off (which you can only figure out by an internet search). This seems very disingenuous on part of Vercel. Make it an "opt-in" or don't fricking track. Conduct a yearly survey or use some other means if you are so interested in improving the framework. I am open to other…

Counter-opinion here: I am the maintainer of one of the most popular plugin for Next.js, and I am cruelly lacking data about how the users of my plugin use it, that would allow me to choose better defaults for it. I don't have access to the Next.js telemetry data, but I could definitely need to ask the Next.js team from time to time: "so, are your users more using Yarn workspaces? Or npm link? Or something else?", et…

I don't think anyone disagrees but lately the society has been talking about something called consent. That matters with software as well.

Re: Next.js 10.2

#46

Post by leerob »

ilumanty wrote: post #44
leerob wrote: post #2

Lee from Vercel here. Happy to answer any questions :) If you have any suggestions for how we can improve Next.js, let me know!

next/image has been terribly slow to generate optimized images since 10.0.7. This issue is a blocker for several people, including myself, and there hasn't been any team response on GitHub yet: https://github.com/vercel/next.js/issues/23637

You can also use any external service for optimizing images if you prefer not to use the built-in WebAssembly solution (which uses Squoosh (https://squoosh.app/). This was announced with the 10.1 blog post: https://nextjs.org/blog/next-10-1#nextimage-improvements

Specific PR improving memory usage: https://github.com/vercel/next.js/pull/23565

Let us know if you're still seeing this issue after updating to 10.2 on the issue linked. Thanks!

Re: Next.js 10.2

#47

Post by leerob »

toastercat wrote: post #40

Can someone explain these frameworks to me? Is Next.js and Gatsby in the same scope? I know they use React under the hood, but are the components rendered server-side? Does that mean no JS is delivered to the client?

Next.js is a hybrid React framework. It aims to improve the developer experience on building web apps by having solid defaults, extensible configurations, and performance optimizations included in the framework.

You can user server-rendering on a per-page basis, as you see fit. Same with removing all JavaScript if so inclined.

More info here! https://nextjs.org/learn

Re: Next.js 10.2

#48

Post by williamstein »

leerob wrote: post #37
cyral wrote: post #8

Earlier quoted context omitted.

I run a pretty complex web app and haven't upgraded to webpack 5 yet with Next. I have some custom webpack stuff so hopefully the migration isn't too painful, but I will report back with the compilation time improvement once done.

Support for webpack 5 has been a multi-month rollout ensuring backwards compatibility. If you do run into issues, please add a reproduction here and we will investigate! https://github.com/vercel/next.js/discussions/23498

Also in the blogpost is the great news: "We're excited to announce Tobias Koppers, the author of webpack, has joined the Next.js team". Thanks for hiring him to ensure webpacks continued support and development!

Re: Next.js 10.2

#49

Post by willemlabu »

I feel like the biggest piece of this announcement was buried at the bottom of the article:

> We're excited to announce Tobias Koppers, the author of webpack, has joined the Next.js team at Vercel.

Re: Next.js 10.2

#50

Post by brundolf »

hijklmno wrote: post #14

What turns me off about NextJS is its "opt-out" telemetry. You have to do a bit of magic at the system level "npx next telemetry disable" to turn it off (which you can only figure out by an internet search). This seems very disingenuous on part of Vercel. Make it an "opt-in" or don't fricking track. Conduct a yearly survey or use some other means if you are so interested in improving the framework. I am open to other…

How bizarre. I've never heard of a framework with built-in telemetry, much less opt-out. I'm surprised this doesn't limit its reach in certain industries.

And this isn't just for their official hosting service? That would be much more understandable

Post reply on HN