Can the Ruby people please stop blogging about Elixir and explain things relative to Ruby? There are way too many 'Elixir-for-Ruby-programmers' tutorials on the net already. Elixir is pretty great and enthusiasm is good but I feel this leaves a large group of people in the dark.
The last thing I want Elixir to be is shoehorned into the web app space and community of Ruby, but it seems inevitable. Oh well.
Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
41–50 of 62 posts
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#42If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
I'm currently working in both. If we are just talking about them in terms of their respective merits, Elixir is my preference. It has a wonderful compiler, pipes allow for composable chains of logic, the Phoenix framework is wonderful for web development. Literally every interaction with it I've had has made me think "wow that's just a great example of excellent programming taste...". In terms of scaleablilty, I've h…
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#43As a Ruby programmer trying to take a look at Elxir, i still find it hard to read. Maybe functional languages take time to get used to but it doesn't seem as "clear" as procedure or oop style. I know the added benefit of speed and concurrency, but for most apps we build it is not needed for now. Do any Ruby programmer find Elxir easier to write or read? Im genuinely curious to hear about this because a lot of Ruby de…
I find Erlang itself to be pretty easy to read and write, if a bit repetitive/verbose at times. There are not very many 'magical' things happening; it's all pretty clearly spelled out. Elixir is mostly an improvement on Erlang unless people are getting crazy with the macros.
In Erlang, I look at 'module_name:function_name' I can simply open the module file and look at the function definition.
In Elixir, I had to ask "Was this function aliased?", "Is it imported from a module? Which module?", "Was it imported/aliased through a use statement?" The code was more concise, but harder to read IMO. Of course you can simply reference functions by their full name in Elixir as well, which is what I'm doing with my own code.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#44Earlier quoted context omitted.
I'm currently working in both. If we are just talking about them in terms of their respective merits, Elixir is my preference. It has a wonderful compiler, pipes allow for composable chains of logic, the Phoenix framework is wonderful for web development. Literally every interaction with it I've had has made me think "wow that's just a great example of excellent programming taste...". In terms of scaleablilty, I've h…
Regarding CI/CD pipeline. I found SemaphoreCI pretty nice. It supports Elixir/Erlang without the need for Docker and can deploy to Heroku pretty painlessly using the available buildpack. Got a full pipeline working for a Phoenix app going in about 30mins.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#45Earlier quoted context omitted.
I'm currently working in both. If we are just talking about them in terms of their respective merits, Elixir is my preference. It has a wonderful compiler, pipes allow for composable chains of logic, the Phoenix framework is wonderful for web development. Literally every interaction with it I've had has made me think "wow that's just a great example of excellent programming taste...". In terms of scaleablilty, I've h…
You mention setting up a Phoenix app in Docker so I'll link to a couple of posts I wrote describing how I do that: https://dev.bleacherreport.com/starting-a-phoenix-project-wi... , https://dev.bleacherreport.com/brunch-in-a-container-phoenix... . I almost always start new Elixir projects in Docker for local development now, and deploy the images to Elastic Beanstalk. If you're not setting up a cluster it's not a bad…
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#46Can the Ruby people please stop blogging about Elixir and explain things relative to Ruby? There are way too many 'Elixir-for-Ruby-programmers' tutorials on the net already. Elixir is pretty great and enthusiasm is good but I feel this leaves a large group of people in the dark.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#47Can the Ruby people please stop blogging about Elixir and explain things relative to Ruby? There are way too many 'Elixir-for-Ruby-programmers' tutorials on the net already. Elixir is pretty great and enthusiasm is good but I feel this leaves a large group of people in the dark.
The last thing I want Elixir to be is shoehorned into the web app space and community of Ruby, but it seems inevitable. Oh well.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#48Can the Ruby people please stop blogging about Elixir and explain things relative to Ruby? There are way too many 'Elixir-for-Ruby-programmers' tutorials on the net already. Elixir is pretty great and enthusiasm is good but I feel this leaves a large group of people in the dark.
The last thing I want Elixir to be is shoehorned into the web app space and community of Ruby, but it seems inevitable. Oh well.
If you want Elixir to remain obscure as well, keep hoping that it doesn't get picked up by web developers and Rubyists.
I for one want the language to eventually overtake Ruby in popularity (hopefully with Phoenix overtaking Rails). So yeah, the more individuals and communities that adopt it, the better.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#49Can the Ruby people please stop blogging about Elixir and explain things relative to Ruby? There are way too many 'Elixir-for-Ruby-programmers' tutorials on the net already. Elixir is pretty great and enthusiasm is good but I feel this leaves a large group of people in the dark.
Perhaps what you mean to say is that you'd like to see more folks in your own communities writing about Elixir with your relevant needs and perspectives in mind.
Re: Learn Elixir with a Rubyist (IV) – Types, Data Structures and Pattern Matching
#50If you had to make a comparison, what would be the pros and cons of using elixir vs node.js?
1. Has a better standard library, plus easy access to all of Erlang's standard library.
2. Handles concurrency, instead of having to rely on an event loop, and does so in a clean and accessible way.
3. Makes it easy to communicate between processes, not on the same machine, but processes running on other machines as well.
4. Is faster and consumes less resources.
5. Is easier to create, manage, and maintain code and deployments.
My last point is subjective, but I like Elixir's syntax much, much better than Javascript's.
In my opinion, comparing Elixir to Node is like comparing a Tesla to a high-end roller skate.