libjpeg-turbo VS bloom

> all decoders will render the same pixels

Not true. Even just within libjpeg, there are three different IDCT implementations (jidctflt.c, jidctfst.c, jidctint.c) and they produce different pixels (it's a classic speed vs quality trade-off). It's spec-compliant to choose any of those.

A few years ago, in libjpeg-turbo, they changed the smoothing kernel used for decoding (incomplete) progressive JPEGs, from a 3x3 window to 5x5. This meant the decoder produced different pixels, but again, that's still valid:

https://github.com/libjpeg-turbo/libjpeg-turbo/commit/6d91e9...

Last vestiges of this fact AFAIK were libjpeg, which had a macro NEED_SHORT_EXTERNAL_NAMES that shortens all public identifiers to have unique 6-letter-long prefixes. Libjpeg-turbo nowadays has removed them though [1].

[1] https://github.com/libjpeg-turbo/libjpeg-turbo/commit/52ded8...

While I think the move to safer code through Rust and other alternatives is a nice breath of fresh air, I doubt you can get these kinds of optimization without using unsafe code in Rust. These optimized implementations often require some kind of safety-bypassing memory modifications to work as efficiently ad they do.

There's a reason https://github.com/libjpeg-turbo/libjpeg-turbo/tree/main/sim... is filled with assembly files with conditional loading.

Sure. You'll see it very often in codec implementations. From rav1e, a fast AV1 encoder mostly written in Rust: https://github.com/xiph/rav1e/tree/master/src/x86

Large portions of the algorithm have been translated into assembly for ARM and x86. Shaving even a couple percent off something like motion compensation search will add up to meaningful gains.

Or the current reference implementation of JPEG: https://github.com/libjpeg-turbo/libjpeg-turbo/tree/main/sim...

zune-jpeg is 1.5x to 2x faster than jpeg-decoder and is on par with libjpeg-turbo.

This is interesting from the standpoint of how new JVM features can be used to improve performance (what I presume the article's main purpose to have been), but the image processing improvement itself isn't head-turning. Also, we've found that libjpeg-turbo (https://libjpeg-turbo.org/) is ~5x (IIRC, can re-run my JMH benchmark if anyone wants me to) as fast for decoding JPEGs as ImageIO, so we wouldn't even benefit from this change in 21 much.

libjpeg-turbo: https://github.com/libjpeg-turbo/libjpeg-turbo/blob/main/simd/x86_64/jsimdcpu.asm

libjpeg-turbo

For all but the simplest formats (basically BMP), the difficulty of implementing encoding/decoding from scratch is significant - well beyond a beginner's ability, and challenging/time-consuming even for senior developers. So, libraries are used in practice - e.g. libpng and libjpeg-turbo.

Static linking is remarkably easy: Creating small Docker images is a delight.

As a data point, I've served millions of HTTP requests using it, without problems.

For larger projects, I think that actix-web is the incontestable winner. That's why it's my choice for Bloom.

For me the worst part was not the job itself (I did ML related stuff) but the environment (commuting, artificial light all day long...).

Since I moved to the entrepreneurship track I'm way more happy. At first it doesn't pay so you need to have savings, but after some time (depends of the person) you start making a living and you can decide on what to work on.

Today, half of my time is dedicated to writing software that I genuinely believe have a positive impact on the world (https://github.com/skerkour/bloom), and half of my time is dedicated to writing and sharing (I'm writing a book).

The best thing that I've understood is that even if my primary skills are programming and architecture related stuff, it doesn't mean I have to code for a living. There are a lot of jobs related to programming that you can switch to.

Hi, I'm not a video game programmer, I mostly do network and web programming, but I do exactly this in Rust and it works very well. Here is an example for a mailer driver, which is a trait and then implemented for multiple "backends" such as AWS SES or SMTP https://github.com/skerkour/bloom/blob/main/bloom/kernel/src/drivers/mailer/mod.rs.

What do you think about degoogle project open source => https://bloom.sh/ " The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more ".

What do you think about degoogle project open source => bloom.sh " The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more ".