3 ms·
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 pr
by davidw 10y ago
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.
- bsuh 10y agoWhile learning Elixir and Phoenix, I found Cowboy source code easier to read with no knowledge of Erlang other than what's inferred from learning Elixir than Phoenix's generated app scaffolding. 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.
- true_religion 10y agoPhoenix tends to do .... interesting things with macros. It's not your typical Elixir application. I find my IDE to be helpful in this situation, since all macros are compile time and thus can be unwrapped by the IDE.
- bsuh 10y agoWhat IDE do you use for Elixir? Thanks.
- true_religion 10y agoI use IntelliJ and Atom. I'm actually still deciding which is better.