Dcraw seems to be only partially gpl - otherwise Adobe couldn't use it in its products. Having a parallel version of the raw converter could yield conversion times far faster then the original C. And it would be a neat Go library to have.
Peter On Sat, Aug 13, 2016 at 5:18 PM, 'Paul' via golang-nuts < golang-nuts@googlegroups.com> wrote: > DCRAW pretty much does it all. Its straight C under GPLv2. Dave Coffin > reverse engineered a lot of stuff to get it to work. It would be a sizable > duplication of effort to try to do all that again. From what I gather even > Adobe uses his stuff. It should be possible to reference his code base in C > and rewrite it in Go, I think. The question would be, what is the point? > Its probably already fast as hell and it likely will not need a garbage > collector. Whatever... > > On Wednesday, July 27, 2016 at 4:36:31 AM UTC+2, Jonathan Pittman wrote: >> >> Well me too! I am looking to see what level of interest there is in the >> Go community to see this happen. I am also looking for people who are >> interested in working on this. >> >> Figuring out how to handle this problem for one specific camera's raw >> files is not too difficult. Figuring out how to do this to handle the >> majority of cases requires a bit more work. >> >> To be clear, I am wanting a pure Go solution that is better thought out, >> better laid out, and better to use than the existing C/C++ options. >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
