4 ms·

So... version 1.0 is basically a shell script that calls libjpeg-turbo followed by jpgcrush?

• michaelmior 13y ago
  No, the jpegcrush functionality is implemented in C as an extension to libjpeg-turbo. But yes, I suppose a shell script would achieve roughly the same result.
  • kllrnohj 13y ago
    So why wasn't this upstreamed to libjpeg-turbo? Why fork at all? libjpeg-turbo is still an actively maintained project after all...
    • riquito 13y ago
      They want to do much more, and with a fork you don't have to justify and discuss every single commit with the original maintainer. If you want to modify heavily something, a fork is the right approach.
    • deleted 13y ago
      [deleted]
    • syntheticnature 13y ago
      Maintainer has different priorities, see https://news.ycombinator.com/item?id=7349117 https://news.ycombinator.com/item?id=7349117
• joshmoz 13y ago
  No shell script or second step involved. Functionality is built in and on by default. This is just a start, we wanted to have something people could use on day one. Further developments to come.
• briansmith 13y ago
  I believe this merge shows the C code that implements the crush functionality: https://github.com/mozilla/mozjpeg/commit/c31dea21188b48498d471650ec1f18bc727c9a36 https://github.com/mozilla/mozjpeg/commit/c31dea21188b48498d...