julio83

Is-it docker compatible?

    The other trade-off that comes from mutable versus immutable data comes from clustering. With Go, you have the ability to make remote procedure calls very seamlessly if you want to implement them, but because of pointers and shared memory, if you call a method on another box with an argument that references to something on your machine, it can’t be expected to function the same way.

I would be happy to know how we can make RPC seamless in GO accross multiple machines (clustering). I've missed a nice lib?

We are replacing all our python backend by golang and indeed static typing is a good way to well structure your data. Regarding reliability, I would prefer elixir for 3 raisons: #1 Functional programming. In go it's really easy to make error by sharing object reference in channel. And what is funny is that it's not so easy to make a deep copy of an object. #2 Goroutine leak and supervision is really difficult to follow. How do you manage it in production ? Thanks to erlang, elixir provides all you need to monitor your green threads. You can even hot fix issues. #3 Beam preemption is clearly a strong winning point.

Bonus point, go scalability is limited to your server. In elixir you can remove server boundaries.

For a new product, I will definitly bet on elixir.

Well, considering the energy put in by US and Russia to divide European union, I will not be surprised... Divide and rule, isn't it?

Thank you X.Niel for 42 and station F.

Sigfox etc.

Well we accept that UK leaves. UK now have to accept to leave the EU market. No issues just clarifications on accountablilities.

Well I am french, top 1 and it's false... Sorry guy just open your eyes and go to the dynamic part of the french society.

Well, getting lost in translation is something normal, isn't it? I have been 1 year in Germany and I tried to learn German. If you don't want to learn a new culture/language it's going to be difficult for sure. Why a whole country should adapt to you? Some english speaking guys don't want to make effort to adapt and I really think that they miss the most important & fun part of travelling/living abroad. You can raise money in english in France. No issue on that.

We have nice startup here and nice developpers. But you can also find nice thinghs in other EU countries. Business is everywhere...

Stick with Go 1.7 means no security update. This give an open highway for hackers to perform large ddos attack etc. Go is amazing. In few lines you have an SSL/HTTP server ready for production. But this is only possible if you are able to deploy security updates.

And IoT companies will have to put trust in another language. We deployed hundreds of ARM5 gateways accross Africa with a golang stack. This kind of decision is not compliant with serious IoT HW providers. Software is easy to upgrade, hardware not. Now we have to bet on another language... welcome rust?

  Go 1.8 will be the last release to support Linux on ARMv5E and ARMv6 processors: Go 1.9 will likely require the ARMv6K (as found in the Raspberry Pi 1) or later. 

Does this mean that we will not be able to produce ARMv5 binaries or this is only a prerequisite for the compiler?