News for hackers. Stuff that matters.
Re:Elixir v1.3 released by yelnatz on Tuesday June 21, 2016 @01:31PM (#11947560)
I use elixir (and phoenix) as well, and this is my biggest gripe with the language.

When reading (and reviewing) code, sometimes you can't logically follow what's going on since most of the code is hidden behind macros.

It's ok if I'm on my IDE that helps expand macros to quickly check the flow, but when it's on a webpage or in a gist somewhere, you're on your own.

Re:Elixir v1.3 released by Donwangugi on Tuesday June 21, 2016 @01:37PM (#11947618)
Which IDE do you use? I have been messing around with alchemist on emacs but the learning curve is pretty steep (i'm not an emacs guru).
Re:Elixir v1.3 released by eddd on Tuesday June 21, 2016 @01:39PM (#11947634)
I can recommend: Atom with https://github.com/msaraiva/atom-elixir
Re:Elixir v1.3 released by davidw on Tuesday June 21, 2016 @02:01PM (#11947889)
Is this a community/culture issue where you can keep things in check if you make a concerted effort to dissuade people from using something too much?

Sort of like Rails was big on testing, which was generally a win.

Re:Elixir v1.3 released by asonge on Tuesday June 21, 2016 @02:22PM (#11948083)
Aside from pretty simple `__using__` macros, most Elixir devs come to appreciate macros and then elect not to use them in the most situations. Most people who do use macros have a very small Macro that just returns the AST for a function call after some tiny little adjustments to the arguments is made.

There are a few exceptions where there are very large projects that make heavy use of macros (Phoenix's router, Ecto), but they are by far the exception. Most of the macros you use every day are simple ones.