On 05/04/2016 01:29 AM, Hayes, Graham wrote: > On 03/05/2016 17:03, John Dickinson wrote: >> TC, >> >> In reference to >> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html and >> Thierry's reply, I'm currently drafting a TC resolution to update >> http://governance.openstack.org/resolutions/20150901-programming-languages.html >> to include Go as a supported language in OpenStack projects. >> >> As a starting point, what would you like to see addressed in the document >> I'm drafting? >> >> --John >> >> >> > > Great - I was about to write a thread like this :) > > Designate is looking to move a single component of ours to Go - and we > were wondering what was the best way to do it.
We discussed about this during the summit. You told me that the issue was a piece of code that needed optimization, to which I replied that probably, a C++ .so extension in a Python module is probably what you are looking for (with the advice of not using CFFI which is sometimes breaking things in distros). Did you think about this other possibility, and did you discuss it with your team? At the Linux distribution level, the main issue that there is with Go, is that it (still) doesn't support the concept of shared library. We see this as a bug, rather than a feature. As a consequence, when a library upgrades, the release team has to trigger rebuilds for each and every reverse dependencies. As the number of Go stuff increases over time, it becomes less and less manageable this way (and it may potentially be a security patching disaster in Stable). I've heard that upstream for Golang was working on implementing shared libs, but I have no idea what the status is. Does anyone know? Cheers, Thomas Goirand (zigo) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
