Hi Jonathan, I think its an excellent idea, and would be possibly interested to contribute. I am not really familiar with libraw, but there would be quite some good reasons to have a pure Go version, as long as not too much work is duplicated: - a pure Go might have cleaner code and be easier to hack - as there just was a remote exploit based on image files, the additional security of Go would be a strong argument - I don't know how much libraw uses multithreading, but a goroutine based code would be nice to utilize modern cpus. - in general it is always good to add quality native libraries to the Go universe. Often people get introduced to a language by the presence of good libraries.
Peter On Wed, Jul 27, 2016 at 4:35 AM, Jonathan Pittman < jonathan.mark.pitt...@gmail.com> 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.
