Yeah. The cool kids are using Erlang. If everybody was doing it, it wouldn't be cool.

I think the "cool kids" part of this is somewhat rhetorical. The whole point of the slides is basically what are the deficiencies of Erlang, and how can we fix them. The results are fairly interesting although not entirely surprising.

It's also worth considering that these questions were asked of Erlang users, so it's the communities opinion of itself. I as an outsider would say my biggest issue with Erlang is that it's a highly event driven system and I don't like event based systems. Events are basically a more opaque form of GOTO and thus suffer the same criticisms. Events are sometimes the simplest way to model something, but as a general paradigm to solve all problems they really suck and do terrible things to your program architecture.

Why do you say Erlang is event-driven? It's a bunch of communicating processes.

>It's above, on both axes Arduino...

Does anyone know why they would include a hardware device among a ranking of programming languages? The most prominent language used to program Arduinos is probably C, followed by C++ and then AVR assembly.

I don't understand why they would include it among programming languages.

From the official docs: "The Arduino programming language is an implementation of Wiring, a similar physical computing platform, which is based on the Processing multimedia programming environment." and "the Arduino language is merely a set of C/C++ functions that can be called from your code."

Just saw this, but please note that Processing is not being run on the Arduino, but rather it is controlling the Arduino through the serial connection. And you can control an Arduino via a serial connection using just about any programming language, including Python and JavaScript.

So again, you can't run Java or Processing on the Arduino. Keep researching.