[nanomsg] Re: mangos, nanomsg, shared libs in Go

  • From: Jack Dunaway <jack@xxxxxxxxxxxxxxxx>
  • To: nanomsg@xxxxxxxxxxxxx
  • Date: Thu, 28 May 2015 12:03:48 -0500

Eagerly awaiting thoughts from @gdamore -- this is very exciting. I am
incredibly impressed by how quickly mangos added WebSocket support and by
the relative SLOC comparison; the efficiency of developing in a
higher-level language is appealing.

Continuing this conversation as an issue in mangos:
https://github.com/gdamore/mangos/issues/138

Kind regards,

Jack R. Dunaway | Wirebird Labs LLC
https://www.linkedin.com/in/jackdunaway


On Wed, May 27, 2015 at 11:01 AM, Jason E. Aten <j.e.aten@xxxxxxxxx> wrote:

Hi Martin,
Yes, that go 1.5 feature is incredibly exciting. Go 1.5 isn't released yet
though, it is due in August.
It would be great to fix the hangs in the C nanomsg code that prevent me
from using nanomsg in production settings in C code, but barring that,
wrapping mangos would be great. Go is indeed much easier to maintain than C.
Jason


On Wed, May 27, 2015 at 5:50 PM, Martin Sustrik <sustrik@xxxxxxxxxx>
wrote:

Hi,

I've just noticed that Go can now produce shared libs usable from C.
Have anyone thought of wrapping mangos in nanomsg-compatible C API so that
one can replace another?

Martin




--
Aurélien Vallée
Phone +33 9 77 19 85 61




--

Best regards,
Jason

--
Jason E. Aten, Ph.D.
j.e.aten@xxxxxxxxx
650-429-8602
linkedin: https://www.linkedin.com/pub/jason-e-aten-ph-d/18/313/45a

Other related posts: