I absolutely love Elixir. It was my first introduction into the world of functional programming and now I miss pipes when I use other languages.
Good syntax (just my opinion)
The API is pretty stable now and I believe the core language is pretty much complete. Because of, upgrading is fairly easy.
Community is friendly and inclusive.
Scales well and a great fit for real time web.
The main ecosystem (Phoenix, Ecto, etc) are excellent.
Great macros support.
The main downsides for me are:
There aren't as many third party libraries compared to PHP/Ruby, so development tends to take longer.
Deployment is better than before, but not as simple as PHP.
No static types.
Currently I'm running it in production on one site (Snipline which uses Phoenix as the backend API) but I have a bunch of side projects that I use it with.
I am a certified trainer that likes to share my knowledge with the world.
Also, I am an adopter of continuous learning and evolving idea.
https://dev.to/wolfiton/who-am-i-3lj7
Not impressed by praprog books when I have to deal with all the errata(mistakes that make the code not work) instead of learning. Even though they tried to cover a lot, the errors just break the experience.
The rest of the sites I agree.
Also, absinthe looks very powerful and clean so far from what I experienced.
Not impressed by praprog books when I have to deal with all the errata(mistakes that make the code not work) instead of learning. Even though they tried to cover a lot, the errors just break the experience.
Unfortunately I find this to be a downside of programming books in general, not specific to pragprog. Many authors don't update their books at all making language updates a real pain to work through. Although many pragprog books are outdated now, from what I've seen most of the Elixir ones are relatively up to date.
Also, absinthe looks very powerful and clean so far from what I experienced.
I've not had the pleasure of trying it yet, but it does look good. Nerves is another great looking library if you're interested in embedded software.
I am a certified trainer that likes to share my knowledge with the world.
Also, I am an adopter of continuous learning and evolving idea.
https://dev.to/wolfiton/who-am-i-3lj7
Elixir has a large ecosystem but unfortunately, it lacks documentation and a lot of up to date tutorials plus libraries or guides on certain things(ex: payment gateway options are limited)
I am a certified trainer that likes to share my knowledge with the world.
Also, I am an adopter of continuous learning and evolving idea.
https://dev.to/wolfiton/who-am-i-3lj7
I am a certified trainer that likes to share my knowledge with the world.
Also, I am an adopter of continuous learning and evolving idea.
https://dev.to/wolfiton/who-am-i-3lj7
I am not referring to your book @stephenbussey, I am referring to programming phoenix 1.4 errata and also to the way The Pragmatic Programmer, in general point of view on learning.
As someone new to the language, the first step is to share code and create your own style but for that you need a template, so restricting what you learn from the books makes this impossible.
Humans are not: copy and paste machines.
You can only use the code in your own projects but can't blog about it or create courses with it. This really sounds odd and doesn't help anyone that really wants to learn.
When you write something you also gain a better understanding of what you learn, it is the natural way to develop your skills.
This is my honest opinion.
I also respect the authors from the Elixir community and consider that they have very useful knowledge to share, but this limitation really is making it hard to do something with that knowledge.
I absolutely love Elixir. It was my first introduction into the world of functional programming and now I miss pipes when I use other languages.
The main downsides for me are:
Currently I'm running it in production on one site (Snipline which uses Phoenix as the backend API) but I have a bunch of side projects that I use it with.
I'll also give a shout out to alchemist.camp, Elixir for Programmers and all the pragprog books for anyone interested in learning Elixir - you won't regret it!
Not impressed by praprog books when I have to deal with all the errata(mistakes that make the code not work) instead of learning. Even though they tried to cover a lot, the errors just break the experience.
The rest of the sites I agree.
Also, absinthe looks very powerful and clean so far from what I experienced.
Unfortunately I find this to be a downside of programming books in general, not specific to pragprog. Many authors don't update their books at all making language updates a real pain to work through. Although many pragprog books are outdated now, from what I've seen most of the Elixir ones are relatively up to date.
I've not had the pleasure of trying it yet, but it does look good. Nerves is another great looking library if you're interested in embedded software.
Elixir has a large ecosystem but unfortunately, it lacks documentation and a lot of up to date tutorials plus libraries or guides on certain things(ex: payment gateway options are limited)
github.com/aviabird/gringotts
Thanks @oshanwisumperuma, unfortunately, it has no documentation for absinthe.
If you look at rails and python they have a lot of options.
Also, a library becomes valid once it has documentation and examples, that is my opinion.
I'm not sure about the other PragProg books, but having just written Real-Time Phoenix, I'm confident in the accuracy of the information.
In general, I've found them to be high quality. If the books are dated because of library changes, that just comes with the territory.
I am not referring to your book @stephenbussey, I am referring to programming phoenix 1.4 errata and also to the way The Pragmatic Programmer, in general point of view on learning.
As someone new to the language, the first step is to share code and create your own style but for that you need a template, so restricting what you learn from the books makes this impossible.
You can only use the code in your own projects but can't blog about it or create courses with it. This really sounds odd and doesn't help anyone that really wants to learn.
When you write something you also gain a better understanding of what you learn, it is the natural way to develop your skills.
This is my honest opinion.
I also respect the authors from the Elixir community and consider that they have very useful knowledge to share, but this limitation really is making it hard to do something with that knowledge.
I'm learning Elixir and already love documentation is easily generated and even tests can be run out of docs!