Introducing the ‘mozjpeg’ Project

Re:Introducing the ‘mozjpeg’ Project by kllrnohj on Wednesday March 05, 2014 @02:07PM (#7349026)

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

[ Parent | on HN ]

Re:Introducing the ‘mozjpeg’ Project by michaelmior on Wednesday March 05, 2014 @02:15PM (#7349072)

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.

[ Parent | on HN ]

Re:Introducing the ‘mozjpeg’ Project by kllrnohj on Wednesday March 05, 2014 @02:18PM (#7349104)

So why wasn't this upstreamed to libjpeg-turbo? Why fork at all? libjpeg-turbo is still an actively maintained project after all...

[ Parent | on HN ]

Re:Introducing the ‘mozjpeg’ Project by syntheticnature on Wednesday March 05, 2014 @03:14PM (#7349544)

Maintainer has different priorities, see https://news.ycombinator.com/item?id=7349117

[ Parent | on HN ]

Re:Introducing the ‘mozjpeg’ Project by riquito on Wednesday March 05, 2014 @02:22PM (#7349138)

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.

[ Parent | on HN ]

Re:Introducing the ‘mozjpeg’ Project by joshmoz on Wednesday March 05, 2014 @02:16PM (#7349090)

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.

[ Parent | on HN ]

Re:Introducing the ‘mozjpeg’ Project by briansmith on Wednesday March 05, 2014 @02:17PM (#7349099)

I believe this merge shows the C code that implements the crush functionality: https://github.com/mozilla/mozjpeg/commit/c31dea21188b48498d...

[ Parent | on HN ]