sharp VS ImageOptim

blur is a technique to blur images while reducing the file size surprisingly. blur works by enlarging the pixels of the image, which reduces the details of the image, and the number of colors also decreases, thus saving storage space. Sharp is a popular image processing library in Node.js, and it supports the blur function. After going through the blur function, the image size at this point is only a few KB, which is reasonable for an image placeholder in the article.

sharp

For simplicity, I will be generating PNGs with JavaScript/Node and the Sharp image library. Any library that can convert between pixel arrays and image files will make the process quite straightforward.

There is also a library that Next.js itself uses: sharp. It can be setup as Node.js service. I even played around a little: image-proxy-service

Sharp Documentation: Link

ESLint does an amazing job in detecting floating promises. I've not had it miss one, ever. When adding this to a project, I've discovered multiple accidental bugs due to a missing "await" keyword--bugs that were extremely subtle and intermittent in many cases.

The only thing it can't do is determine that you actually did handle the promise later. Which is fine. It's a LINTING RULE, and false positives are the name of the game.

What's BAD is when you accidentally miss handling a promise at all. It's an invisible error without the linting rule.

Your other comments...don't even make sense. You're going to build a Lanczos filter by hand? Or you're only going to ... compile ImageMagick to WebAssembly?!, ... an implementation which is tremendously slower (nearly unusably so for large images) than that of Sharp:

https://www.npmjs.com/package/sharp

... which is simply an import away?

No, what you're doing is called "motivated reasoning." You've concluded that Deno is the best, and you're reinterpreting all of my complaints in convoluted ways to support your predetermined conclusion.

Standard fanboy behavior. Or troll behavior. I cite Poe's Law as why it's impossible to tell the difference.

Compressing images: This technique reduces image size without compromising quality. You can achieve this using various image compression tools like TinyPNG or ImageOptim. These tools are specifically designed to manage multiple image formats and compression methods. They help reduce image files, resulting in less data transfer from the server to the user's device. It is advisable to compress images before uploading them to the web server.

ImageOptim: ImageOptim is a free and open-source tool that can be used to compress JPEG, PNG, and GIF images.

Currently installed apps: Alfred for searching applications/files and launching websites quickly i Stat menus to monitor my hardware Geo Gebra Classic 6 for school Rectangle for better window management Obsidian for note taking Resolve for video editing and all utilities that come with it Bitwarden as my go-to password manager Microsoft Word, Excel PowerPoint and Teams for school Dropover for moving or sending more files quickly Gestimer for work sessions iTerm as a better terminal than the built-in one Python and all things that come with the install Parallels Desktop and all stuff that comes with the install for running windows only applications Visual Studio Code for coding Blender for 3D Image Optim CurseForge for modded Minecraft Minecraft Find any file Mac Updater 3; would love to have the pro version

ImageOptim - file resizing and optimising images, even on the command line (free)

ImageOptim - Price: Free Image optimizer for Mac that allows you to reduce the file size of your images without losing quality, and strip the metadata.

If you're on a Mac, use ImageOptim to optimize your images: https://imageoptim.com/mac If you're on Windows, I imagine there's a similar app

Bonus points: before you re-import them drop the exports folder into imageoptimfor the most efficient lossless compression imaginable.

ImageOptim — shrink those file sizes!