Live data from Hacker News

Next.js 10

nextjs.org

51–60 of 206 posts

Re: Next.js 10

#51
Looks cool. The scope this asks for in GitLab is too much (everything):

  This application will be able to:

  Access the authenticated user's API
  Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry.

Re: Next.js 10

#52

I’m not a fan of these frameworks. They add another giant layer of stuff to learn and understand. I’d rather just program react and the browser instead of hoping some framework will do it all for me.

Next really doesn’t add a giant layer of anything, it’s almost vanilla React aside from their own routing and the server side functions (which you can start out not using)

Re: Next.js 10

#53
post #45

I have mixed emotions on this framework. If you're doing a simple project, Next is the best around. Also great for marketing pages, etc. But if you have a more sophisticated app, with an API, page routes that need to toggle based on cookies, etc, then you have to integrate something like Express. I've done this several times with Next, and it just doesn't pay off. I've also tried to use it at work, but it changes rap…

Yeah, I think it's going down the VC wormhole right now. It was a fantastic microframework for doing a few core tasks extremely well. Creating a fully-managed hosting platform is a good revenue stream to support the development. Adding analytics and commerce with vendor tie-ins seems like serious mission creep.

Re: Next.js 10

#54
post #40

> Nowadays users browse the web using their phones, tablets, and laptops, yet images are still as a one size fits all. For example: sites load a 2000 by 2000 pixel image, but phones are only displaying it as 100 by 100 pixels. That's what srcset & were invented for. > Furthermore, 30% of images on web pages are outside of the initial viewport, meaning the browser loads images that a user does not see until they scrol…

Is srcset commonly used? I am not familiar with it but I'm more full stack than frontend and often feel like front end moves faster than I can keep up with.

I don't know about its popularity, but it works as advertised and my company had used it. What's more important is that it's a correct solution for the problem (unless old browser support is required).

Re: Next.js 10

#55
post #40

> Nowadays users browse the web using their phones, tablets, and laptops, yet images are still as a one size fits all. For example: sites load a 2000 by 2000 pixel image, but phones are only displaying it as 100 by 100 pixels. That's what srcset & were invented for. > Furthermore, 30% of images on web pages are outside of the initial viewport, meaning the browser loads images that a user does not see until they scrol…

Is srcset commonly used? I am not familiar with it but I'm more full stack than frontend and often feel like front end moves faster than I can keep up with.

> Is srcset commonly used?

It is, to provide a couple of different image sizes so smaller screens/high DPI devices can load the best-sized image for their use.

This is the best article I know on the subject https://cloudfour.com/thinks/responsive-images-the-simple-wa...

Re: Next.js 10

#56
post #33

As someone who only really built websites using jQuery / custom vanilla js and good ole CSS2, this stuff feels completely alien to me

Same. I mean I understand how it works but I ask myself what's the point every time. I've looked into react and I hate how it works and I hate how every 2 months people are begging for some new optimization because its slow and sucks. Then version 5000 is released and fixes that slowdown, but every react site I've ever used is still buggy and slow as hell.

*laughs in modern web development

Re: Next.js 10

#57
post #40

> Nowadays users browse the web using their phones, tablets, and laptops, yet images are still as a one size fits all. For example: sites load a 2000 by 2000 pixel image, but phones are only displaying it as 100 by 100 pixels. That's what srcset & were invented for. > Furthermore, 30% of images on web pages are outside of the initial viewport, meaning the browser loads images that a user does not see until they scrol…

> That's what srcset & were invented for.

Next.js is going to be using srcset under the hood, I'm sure. The whole point of Next.js is to make best practices like this defaults, not to do anything groundbreaking and new.

Re: Next.js 10

#58
post #21

Earlier quoted context omitted.

The React team is or was reportedly working on "progressive hydration" which sounds like what you're talking about. This tweet from React core team member Dan Abramov in December 2018: https://twitter.com/dan_abramov/status/1079352276433715200

They've been talking about it for years alongside with SSR streaming. Nothing concrete so far.

I get the sense the React team don't really care about SSR as it's not a massive use case for FB.

Re: Next.js 10

#59
post #40

> Nowadays users browse the web using their phones, tablets, and laptops, yet images are still as a one size fits all. For example: sites load a 2000 by 2000 pixel image, but phones are only displaying it as 100 by 100 pixels. That's what srcset & were invented for. > Furthermore, 30% of images on web pages are outside of the initial viewport, meaning the browser loads images that a user does not see until they scrol…

Is srcset commonly used? I am not familiar with it but I'm more full stack than frontend and often feel like front end moves faster than I can keep up with.

[deleted]
Post reply on HN