Next.js Adventures: Some Blasphemy Against the Holy Image Component

Posted by sashevuchkov on Saturday July 09, 2022 @09:34PM
from the buhalbu.com dept.

https://buhalbu.com/stream/next-js-adventures-some-blasphemy-against-the-holy-image-component

( 3 comments | 3 points | on HN )

Re:Next.js Adventures: Some Blasphemy Against the Holy Image... by mr90210 on Saturday July 09, 2022 @10:39PM (#32041351)

I’ve felt your pain. We run a Next app on Heroku and we had to disable such component because it was making the app consume in average 500mb of RAM. Our app doesn’t do anything special nor we have many visitors.

[ Parent | on HN ]

Re:Next.js Adventures: Some Blasphemy Against the Holy Image... by sashevuchkov on Sunday July 10, 2022 @03:55AM (#32042700)

Yeah, that's my other pain point - the higher usage of CPU & RAM.

[ Parent | on HN ]

Re:Next.js Adventures: Some Blasphemy Against the Holy Image... by sashevuchkov on Saturday July 09, 2022 @09:34PM (#32041066)

If you believe that the <Image /> component is the finest solution for handling images ever invented, then I suggest you stop reading right now and go find other interesting stuff.

[ Parent | on HN ]