Also, please keep tedious programming language flamewar like this and https://news.ycombinator.com/item?id=29288298 off HN. We're trying for something more interesting here.
https://news.ycombinator.com/newsguidelines.html
Edit: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... is totally unacceptable, and we ban accounts that carry on like that. I don't want to ban you, so please don't post like this again. In fact, please just stop posting about this topic and stick to things that genuinely gratify your intellectual curiosity. Conducting a putdown campaign against what other people like is an abuse of this site.
that's basically what you just did. "Electric cars will pollute someday! Just you wait!" >..<
Keep in mind that I've worked on small Ruby projects as well, and still prefer Elixir.
I'm not gonna suggest that there wouldn't be challenges in that scenario, but it just seems to me so far that they'd be much more manageable given the thoughtful design of Elixir.
The biggest problem in my app currently is actually JS/Node dependency hell, not Elixir code... and the JS only makes up a small portion of my app! (I should have never used AdminLTE as a design template...) At least my JS is tested (which was another huge PITA to figure out... simulating a DOM...)
It's been years of this nonsense. Let it go.
Not sure what you mean here specifically (do you not understand Enumerable.inject in the Ruby stdlib? That's about the hardest thing to understand and once you're there, functional langs are pretty trivial) I was already coding in a functional style in Ruby (PORO, intentionally not mutating vars, etc.), so that wasn't an issue for me at least, when I hopped to Elixir.
The kicker was when I spent an entire month debugging a problem that would have been impossible to occur in Elixir/Phoenix- I was working on a million-line Rails codebase and there was a session issue where sessions would seemingly randomly get dropped... it was nondeterministic and absolutely maddening, a number of other devs had attempted to fix it and failed, and I finally did- and it ended up being a key-overwrite issue with a regular Hash being merged with a HashWithIndifferentAccess in the ENV variable passed between rack layers (and god, was that hard to find! I had to write custom debugging tools that walked through every Rack layer and deep-diffed the ENV hash, etc.). That was the last straw.
So far, Elixir/Phoenix has been fantastic for me at NOT producing "flagging tests", nondeterministic-seeming bugs, etc. Massive productivity boost.