Elixir Release v1.0.0
21–30 of 42 posts
Re: Elixir Release v1.0.0
#22Really happy to see the 1.0 milestone reached. I've enjoyed my time with Elixir. It's really approachable, and made a lot of Erlang/OTP concepts start to click for me in ways that they just hadn't, before. Syntactically, it's a pleasure to use as a long-time Ruby guy, which I suppose is no surprise given José's presence in the Ruby community. However, all of this aside, what makes me the most excited about Elixir is…
Lack of jobs is a problem :( It is a nice language but has stiff competition from Go.
My company is currently looking for Elixir/Erlang devs to help us build a new decentralized communication platform. Based in London/SF.
If you or anyone is interested, please ping me at ryan@spatch.co.
Re: Elixir Release v1.0.0
#23Is it recommended that you learn Erlang before you learn Elixir, or can you jump straight into Elixir without Erlang knowledge?
Disclaimer: I studied Erlang before Elixir, so I don't have a fresh perspective.
Re: Elixir Release v1.0.0
#24Earlier quoted context omitted.
Hah, yeah, let's port everything for no obvious reason.
Erlang and Elixir play very well together. I imagine Erlang shops "moving to Elixir" will be in the form of Erlang shops hiring people with Ruby experience and letting them use Elixir so they can get up to speed faster.
Re: Elixir Release v1.0.0
#25A genuine non-flamebait question - if one were to write a Whatsapp-like messaging system today , would you use Erlang, Elixir,Scala,Java 8 or Go? I'm kind of wondering whether Go is not already eating into Erlang (and Scala). I am not an expert, but I understand that Go is not at par with Erlang today , but I am wondering about a 3-year bet for a startup.
Re: Elixir Release v1.0.0
#26A genuine non-flamebait question - if one were to write a Whatsapp-like messaging system today , would you use Erlang, Elixir,Scala,Java 8 or Go? I'm kind of wondering whether Go is not already eating into Erlang (and Scala). I am not an expert, but I understand that Go is not at par with Erlang today , but I am wondering about a 3-year bet for a startup.
Re: Elixir Release v1.0.0
#27A genuine non-flamebait question - if one were to write a Whatsapp-like messaging system today , would you use Erlang, Elixir,Scala,Java 8 or Go? I'm kind of wondering whether Go is not already eating into Erlang (and Scala). I am not an expert, but I understand that Go is not at par with Erlang today , but I am wondering about a 3-year bet for a startup.
Go can try to reach parity with Erlang one day...but Elixir already is Erlang...That combined with the fact that Elixir's package management already feels light years ahead of Go's disaster and I think it's a winner. I'm sure I'm wrong and the flames of Go lovers will engulf me in the responses, so take this with a mountain of salt.
Re: Elixir Release v1.0.0
#28Earlier quoted context omitted.
Hah, yeah, let's port everything for no obvious reason.
Erlang and Elixir play very well together. I imagine Erlang shops "moving to Elixir" will be in the form of Erlang shops hiring people with Ruby experience and letting them use Elixir so they can get up to speed faster.
Elixir is more visually similar to Ruby, sure, buts its substantively not very similar, so the visual similarity is, if anything, a detriment, IMO.
Re: Elixir Release v1.0.0
#29A genuine non-flamebait question - if one were to write a Whatsapp-like messaging system today , would you use Erlang, Elixir,Scala,Java 8 or Go? I'm kind of wondering whether Go is not already eating into Erlang (and Scala). I am not an expert, but I understand that Go is not at par with Erlang today , but I am wondering about a 3-year bet for a startup.
I would definitely go for either Erlang/OTP or Scala+Akka. No other platform you mention has built-in support for clustering to the extent that OTP and Akka do.
Re: Elixir Release v1.0.0
#30Is it recommended that you learn Erlang before you learn Elixir, or can you jump straight into Elixir without Erlang knowledge?
By "programming model" I mean things like immutability, concurrency, fault-tolerance, and the way you design systems with OTP.