Network Autoconfiguration with Go and ØMQ | Hacker News Reader

Network Autoconfiguration with Go and ØMQ

kyleisom.net

37 pointscpg12 comments

I wonder if the Zero-MQ guys knows that the letter Ø is almost identical to the symbol Ø and that it is pronounced "uh".

To people not using these letters on a daily basis, I'm sure it looks cool, in a bork swedish chef way, but it probably doesn't internationalize very well.

Tell me about it. I get the same thing with the fake-Greek letters everywhere, e.g. hλlf life (which I read as hllf), GRΣΣK (grssk), etc. It's infuriating.

Similarly nasty is the use of Cyrillic to create fake Russian, as in TЗTЯIS (which would be pronounced as "tztyais").

Yep, I guess тетрис doesn't look English enough.

Not to mention that the symbol they picked is null, not zero. There's a subtle mathematical difference.

I just call it ZMQ or ZeroMQ. Most style guides (or langauges themselves) prevent you from naming a class 0MQ, so I just pretend like nobody calls it that.

But do you pronounce it Zed or Zee?

Zee.

I've actually always slashed my zeros from left to right because my phi's end up being slashed right to left.

Welcome to my world whenever I read "Motörhead" or "Blue Öyster Cult".

I still cringe every time I see the transportation startup's misspelled name (Ueber/Über) as Uber.

Just curious by looking at the snippets of code, why not make the code address-family agnostic?

The server should listen on both ipv6 and ipv4 at the same time (on linux at least, if you open a listening socket on ipv6, it will also accept ipv4 connections, so no need for duplicate code) and send advertisements on ipv6 and ipv4 as well.

The client should listen to advertisements on both address families, connect to whatever addresses it discovers : ipv6 first, then ipv4.

Also, having your own discovery/advertisement mechanism has its merits, but have you considered avahi/zeroconf/bonjour?

Reply on news.ycombinator.com