Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
1–10 of 62 posts
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#2If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#3If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
What's your use case?
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#4If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
More fair comparison would be Phoenix [1] to node.js
Elixir is a programming language whereas node is a framework.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#5If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
@aecorredor, there a bunch of things you should consider and that I could use to compare both, in general ppl tend to compare elixir with node because it also enables you to build concurrent apps, but you have to take into account the Erlang VM and OTP, the tools it brings to the table to build concurrent system surpass node.js capabilities of delivering the same thing IMHO. Also don't forget that Erlang and it's VM has 30+ years of intense exposure to different scenarios and apps, and put that together with 30 years worth of open source work and libraries. I'm not saying node.js is bad, or even worse, but maybe both shouldn't be compared because represent different tools for different jobs.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#6If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
What's your use case?
I know depending on the use case some tools are better than others, but to clarify my original question, for someone who might just be getting into the back-end and looking towards the future, what would be a better choice to focus on, elixir or node.js? and say for example that the person has done both some Ruby and JavaScript programming, including some basic apps with Rails and Express.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#7If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
It does depend on what you are doing - if you are making websites both are fine (although I've seen callback hell implemented in a Node/express website before).
If you have difficult scaling problems that need stateful servers and clever cross server web socket implementations like Phoenix.Presence or 2 million web socket connection on a single huge machine, Elixir with the OTP is more likely to give you tools to build this difficult to scale thing.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#8If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
More fair comparison would be Phoenix [1] to node.js Elixir is a programming language whereas node is a framework. [1] http://www.phoenixframework.org/
True, then in that scenario we should talk about comparing phoenix and express right?
edit: meant to say phoenix, not elixir.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#9If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
More fair comparison would be Phoenix [1] to node.js Elixir is a programming language whereas node is a framework. [1] http://www.phoenixframework.org/
Node isn't really a framework, it's a runtime and is fairly close to a language. It's roughly analogous to Nashorn.