bontoJR

1. Both communities are big enough, if you are in Asia, gophers are everywhere

3. If you don't have any knowledge about functional programming, Scala will open you a new world. It will force you to think in a different way and will introduce you to many new concepts in how to solve parallelism and asynchronous computation using easy concepts like immutability or far more complex like functional reactive programming or duality.

2. I worked with both languages, I liked the fact I was able to write a whole, easy, REST web app in just half a day with Go, but the syntax and the verbosity in error handling, made me kind of crazy. I would definitely say that is a very good language, extremely fast compared to others like Ruby or Python and it can be even a very good complement to Scala.

Scala is my favorite language, by far, for server side projects. It requires time to be mastered, there's never a "Scala way" or a single way to solve a problem, but there's (almost) always a best solution. Twitter's scala school[1], for example, is a good place to see examples about when and how to use certain language features. The fact that runs in the JVM, a Virtual Machine with 20 years of development, improvements and optimizations, is almost a killer reason to pick Scala. I worked with Java/Spring/Hibernate in the past, a very frustrating experience, but Scala changed my mind about the JVM and opened a completely new world: Functional Programming. Now I know and use concepts like Monoids, Monads, Future/Promises, Reactive Programming, Actor Model, Duality, etc... without any problem. It's a complete different world and I think it deserves a shot.

[1] https://twitter.github.io/scala_school/

Google used to have a very bad reputation about customer service, but in the last 2-3 years they focused on fixing some of these problems. I can't really say they are bad anymore, at least they are in the average, for some products they are excellent. That's my experience.

I actually don't because I have no clue how Windows Server works. So this attack hits the kernel and the context is low level, right?

That's a good point, because in the example we can clearly see how to check if a system is or not patched and that, using this attack, we can crash a Windows Server.

The remote execution part is completely missing (fortunately), but I was wondering if this gives the admin rights on machine (I have absolutely no experience on Windows Server machines, so I don't know how it works in terms of services, permissions and roles).

Yes, exactly. The EU has the power to do something on this. Actually, when US was facing the Net-Neutrality case, most media questioned about what EU was doing about the same topic and they all pointed out that, according to many different lawyers, this is a field where the EU can interfere.

So, I don't have doubts about the fact that EU has the right and the power to do something.

> "you're either with us or you're a terrorist"

It looks like is a very common argumentation for politicians. Another one is: "You don't have to care if you don't have anything to hide".

I think both paths are extremely and deeply wrong. We can't put in prison the whole Afghanistan's population because just thousands of individuals embraced terrorism, in the same way we cannot track an entire nation just because 8-9 people are planning a terrorist attack.

There are way healthier to do it.

I used OVH services for a long time, very good customer support, best quality/price ratio for Europe and some of their machines are extremely good. It would be a shame for France to lose them.

France is known to be very interested in mass surveillance, but what scares me most, it's that the European Union seems completely ignoring the topic, leaving countries to deal with this topic. I am lucky to live in Europe, but outside the EU, so we don't have to deal with these strange regulations, but I am concerned about the impact that this law can have in a short-mid future with all other countries. I really don't want to see UK, Germany, Italy, Spain, etc... follow the France's example, starting to roll-out laws in the name of security and terrorism fight.

This must be stopped at a higher level (EU), because also other countries are extremely interested on this topic.

Did you have to change anything during the implementation? What about habits compared to deploy on VMs/DSs? What's you experience regarding a long running? Did you face any issue?

I went to a couple of events where Docker was a topic in Europe, the general feeling is that the solution looks great, but every single time a speaker/organizer asks to raise a hand if using it in production, nobody does. I mean, it's definitely a technology having a momentum, but I still have to find someone that heavily used it in production.

Great piece. In fact, this is another big topic. I can't image a bank switching technology in a such easy way for components that maybe are critical.

A technology switch can have multiple sides, sometimes the success is way beyond expectations and the current implementation doesn't fit the real requirements, making the switch looking more to a success rather than a failure. On the opposite it's very common to have the exact same problem you described, new trending technology picked, hit the limit, switch to and old more robust solution, this is definitely a failure and is something managers don't like.

I faced a similar problem with Mongo 2 years ago, had the same switch to PostgreSQL.

I don't see anything wrong here either, I kinda like the fact that as engineers/developers/coders we still have the opportunity to admit that an early stage decision doesn't fit our needs anymore and we can then change.

The switch from Node to Go seems quite popular right now and it honestly makes me thing there's something wrong with the general perception of Node.

We are currently in a world where we have a huge amount of traffic on almost every web app with just a discrete success, but we still make the mistake to pick a technology that seems "good enough", instead to pick a "great one" because looks slightly harder to manage/learn/deploy. I know that during the early stage, pace is very important and RAILS or Node are easier and faster to handle compare to Scala or Erlang, but sometimes another technology at the beginning would save a lot of headaches and night calls. We still fail at the very early stage to choice the right technology, but nobody is afraid to admit it and to switch, I find this amazing.

This phone made me think a lot about the future of mobile in emerging markets. I was reading a lot of great feedbacks about Mozilla with Firefox OS in Africa and some South American countries, they are very happy about the price/value of devices and the fact that these countries have a very basic (or even no) infrastructure, makes them very interesting for these systems, because you can actually build from scratch, using pretty recent technologies.

All this introduction is to try to understand the Ubuntu Phone world, I don't think it can emerge against Android or iPhone, so it should definitely compete against Mozilla in emerging markets, but it looks like is coming a little bit late. I am also curious about how developers will react to the platform, with a native or HTML5 approach, looks similar to the Microsoft strategy. Firefox was able to get devs easily because the HTML5/Javascript is an easy combo and is widely known, native development requires more efforts and has a steeper learning curve. A smartphone is 20% platform and 80% ecosystem, no apps means no users.

I am honestly interested in trying it, I did it for Firefox, writing a simple weather app for it, so I would like to do the same. At the moment, I am not sure the system will be able to compete, but happy to be proven wrong!

That's exactly what I mean. Running as fast as possible minimize the chances to recover from errors and puts a lot of pressure on the working team. I know it's not just about companies. Anyway, don't get me wrong, between the 2 I would go for the Silicon Valley model all the time. ;)

I actually work in Zürich! Definitely!

Welcome to Europe.

Comparison between Europe tech startup scene vs the Silicon Valley one is quite unfair. I am based in Switzerland, you cannot imagine how hard is for a tech (worser if service) company to raise money. The model is extremely broken because the mind of an average European investor is completely different respect to the average American investor. In US the normal startup funding process works around a working prototype and how fast you can ship, in Europe, mainly here in Switzerland is about the protection you can give to a product with trademarks, patents and other things. So when you ask for money the first question is: is it protected? Or, can we protect it? Are barriers good enough so we can skip short-term competitors?

The second huge problem is the exit. In US, the IPO is a kind of fallback alternative to the acquisition, that is the main goal in a reasonable amount of time, so this makes the IPO not the favorite exit-strategy at all. In Europe it's actually the same, but the acquisition model simply doesn't work. You don't have any big tech company here giving the real exit-strategy option to investors. So the only chance you have to get them, is to prove that you can literally make a certain amount of money even in the worst case. Nobody believes that Apple, Amazon, Google, Facebook or whatever can acquire a Swiss startup company in the first 5 years of its life, so the result is that tech companies can barely raise money.

IMO, the Silicon Valley model is very risky, the motto "fail fast, fail often" is certainly attractive, but has a lot of downsides for funders and people involved, on the other hand the European scene is too slow, too hard and is always complaining about the fact that we are unable to compete against the Silicon Valley. I think the right balance is required, but it's just an opinion.

This is really interesting. It's very annoying to always fire the browser the renew/buy a certificate. I would definitely git it a shot for a standard one, the wildcard looks quite expensive honestly. In other sources you can find it at half-price with promo codes.

Legalization has been always proved to be effective as coutermove to illegal traffic and, on the other hand, it's a great money source for the state applying taxes. Now, the problem now is that regulations must be clear and the price well balanced to avoid the black-market price war.

Absolytely a good reading. Sometimes this kind of readings can help in a complete different problem. Sometime happens you are dealing with another problem, then you remember this story, and you figure out what's wrong because there're some similarities. I remember to have fixed a problem with Postgresql remembering a story about Unicode and Postfix, different domain, but similar problem.

I am 28 and I am actually in a similar situation, but honesly in the last months, my mind started to chillout about getting old with the risk of stay behind. It doesn't really matter the age of a developer, but the most important thing is the curiosity about what he does. A developer without curiosity is a walking-dead-dev, you can be passionate (I don't like the word itself because means suffer in latin) and love your job, but the curiosity is what makes a developer shine. So, unless you lose this, you don't really have to worry, try to learn always as much as you can and keep going on, you will definitely find your path and the way to enjoy what you do.

Well, there's a micro-kernel... :D

Now, the question: why?