I don't know what the true story actually is, however some camera hardware makers such as Nikon are giving software developers a tough time by intentionally obfuscating their metadata. A lot of folks had big problems with that including adobe. I just mentioned "reverse engineering" to indicate a potential for far bigger mess. Enough said.
I was not aware of Rawspeed. I do not have any personal preferences, all I was saying is that a lot of hard work has already been done and it would be reasonable to try and leverage it. Go language would be good, I think, because a lot of programmers that would like to help out in opensource image processing drop out when they discover C++ is just to hard. They try for a while and then they just give up. Maybe Go language has the potential to bring some change to that problem. 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.
