On Fri, 8 Nov 2013 14:43:48 +0400
Peter Lemenkov <lemenkov(a)gmail.com> wrote:
CC: Dan Horák, Jeffrey Scheel.
Hello All!
I'm going to speak at the next Moscow Golang User Group this November
and will describe some of Fedora Golang SIG plans. Here are the slides
(in Elglish and in Russian):
*
http://peter.fedorapeople.org/presentations/Moscow%20Golang%20Users%20Mee...
*
http://peter.fedorapeople.org/presentations/Moscow%20Golang%20Users%20Mee...
I won't talk about Docker (my fellow golangers from Yandex will do),
and won't tell anything about etcd (we still don't decide what to do
with it). Instead I'll describe my effords to fix long-standing issue
with systemd and multiple Erlang nodes running in parallel. I did few
attempts to fix that issue with different success, and finally
switched over to golang-powered solution which fixes it (and makes a
room for further improvements).
This will have an interesting consequence for the secondary arches,
such as s390/s390x and PowerPC. In the future all Erlang services in
Fedora, namely CouchDB, Ejabberd, RabbitMQ, Riak, will *want* service
written in golang (I wouldn't use word "*require*" here). Since golang
is available only for x86/x86_64 and ARM, this could be an annoyance.
Technically it will still be possible to run Erlang daemons on the
secondary arches, but it will require some painful manual
intervention, and lead to inevitable race conditions. Beware! Also I
hope we'll see some progress on porting Golang on these achitectures.
Is there a strict dependency on golang or just on go? Because "GCC
4.8.2 provides a complete implementation of the Go 1.1.2 release."
citing from gcc 4.8.2 release notes and we build gccgo on all our
secondary arches.
Dan