News for hackers. Stuff that matters.

A comment on Introducing the ‘mozjpeg’ Project. Parent comment

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 ]