3 ms·
I think a lot of this is subjective and context dependent so the definitive “this is good” and “this is bad” language was a bit of a turnoff. BUT, I did like s
by mattbaker 5y ago
I think a lot of this is subjective and context dependent so the definitive “this is good” and “this is bad” language was a bit of a turnoff.
BUT, I did like seeing someone’s point of view with thoughtful explanations and examples, kind of like what you get out of a good discussion at an elixir meetup or something :D I enjoyed reading it.
- keathley 5y agoCalling it "good and bad elixir" was probably overly charged. Its a little late to change it now, but something I'll consider in the future.
- acrispino 5y agoI don't see how it's too late, unless HN commenters from today will be the only audience. You could also add an note.
- hdra 5y agofwiw I enjoyed the article, i agreed with some of them, disagreed with the others, but overall I liked the perspectives presented in the article... can you elaborate more on the "Don’t pipe into case statements" point though? Not entirely what you're saying with this one as there isn't any explanation why one might be better/worse than the other, other than aesthetic/personal preference. Needing to access the result from the previous pipe in the case maybe?
- dnautics 5y agodon't feel too bad about it: It would probably have gotten fewer eyes if you had named it more mildly.