sharp VS jpeg-xl

Last thing left is to use our new upload function in our server action. Since I like to upload images in single format and have some more control over them, I will additionally use sharp library. For file name, I'll generate some random string using nanoid:

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.

shit i did not know that.. does it also work well with wordpress etc? because the only downfall of avif is bunch of extra steps on a nginx to get it to work right.. Also, u/LITUATUI 's comment, do i just change avif to jpeg-xl? i found something but didnt fully finish reading yet https://github.com/ImageMagick/jpeg-xl

One of the most interesting things to me is that JPEG-XL is under an open Patent License, unlike the original JPEG.

https://en.wikipedia.org/wiki/JPEG_XL

Also, Google contributed quite a bit to it's development. As the patent grants show:

https://github.com/ImageMagick/jpeg-xl/blob/main/PATENTS

https://github.com/libjxl/libjxl/blob/main/PATENTS

Microsoft seemed to have gotten a patent on part of it's implementation (which Google also tried to get). Not sure if Google will pay to invalidate that patent, but I have a feeling they are more likely to defend AVIF.

https://www.theregister.com/2022/02/17/microsoft_ans_patent/

Google's control is a little concerning, but I do feel there are bigger fish to fry then choosing between two free formats. Like H.264 and H.265 patents.