Why Elixir (2014)

Re:Why Elixir (2014) by brightball on Friday August 18, 2017 @09:27AM (#15045873)

If you're doing anything at all server side, you have a use case for Elixir.

[ Parent | on HN ]

Re:Why Elixir (2014) by pjmlp on Friday August 18, 2017 @01:02PM (#15047868)

Already covered by the JVM and .NET on my toolbox.

[ Parent | on HN ]

Re:Why Elixir (2014) by brightball on Friday August 18, 2017 @01:36PM (#15048155)

Sure. So why does any other language need to exist?

Technically, this stuff is all covered by any preceding language in the toolbox. We could all just use C...or Perl?

Why bother to learn the JVM languages when C already had it covered?

Simple...because you can do it better.

[ Parent | on HN ]

Re:Why Elixir (2014) by pjmlp on Friday August 18, 2017 @02:05PM (#15048416)

Languages get used because they cover specific use cases or libraries.

UNIX -> C

Browser -> JavaScript

Data Science -> Python, R, Julia, Chapel, C++

Windows Development -> .NET languages, C and C++

Android -> Java, Kotlin, C and C++

macOS, iOS, tvOS, watchOS -> Objective-C, Swift, C and C++

Docker, Kubernetes -> Go

Game development -> Assembly, C, C++ and C#

High performance data switches -> Erlang

Of course one is free to use outlier languages and try to bend them into specific use cases, but then one also has to live with less tooling as the ones that are the "platform language" for the specific use case.

Throughout my career I always kept an open mind to try out new programming languages and paradigms, but in what concerns production code I learned the hard way to only use the official platform languages.

[ Parent | on HN ]