4 ms·

Incredible. Been using this stack for an year and I'm super excited for the future. Lately I also do see multiple new companies picking it up for different work

Incredible. Been using this stack for an year and I'm super excited for the future. Lately I also do see multiple new companies picking it up for different workflows and applications. Though it may not reach Ruby levels of popularity, it's still just fine. Learning curve is favorable, performance is stellar, and the toolkit that comes with the language is quite featureful. I see other languages borrowing elements from Elixir - especially LiveView and Pattern Matching. The only hiccups I faced where when I had to roll out my own solutions for a few things (a background job processor, error manager, a mocking module for unit tests, etc.) Even with all this, I'd still say Elixir is worth it, given the performance gain and the patterns it enforces. It all just makes the code easy and understandable.

pselbert 6y ago
Rolling your own tools is an irreplaceable way to learn things thoroughly. That said, HN readers from outside the Elixir should know there are great libraries for all of those use cases. Point in case is background job processors—we have plenty of options, though I’m especially fond of Oban[0] (full disclosure, I’m the author). [0] https://github.com/sorentwo/oban https://github.com/sorentwo/oban
- princevegeta89 6y ago
  I got into it before Oban was ever released. However, it seems like a solid solution. I've looked at Faktory as another great option as well: https://github.com/contribsys/faktory/ https://github.com/contribsys/faktory/
  - dnautics 6y ago
    haha, yeah the annoying thing about elixir is that sometimes, you give up, roll your own solution (because it's not terribly hard to do), and then right after you're done, some team has built a slightly better solution (because it's not terribly hard to do).
- AlchemistCamp 6y ago
  > Rolling your own tools is an irreplaceable way to learn things thoroughly. I completely agree. It's also a great way to avoid complexity you don't need. There are limits, but especially while learning I like to err on the side of fewer dependencies. BTW, I just now saw that getoban.pro was a thing. It looks great!

pselbert 6y ago

Rolling your own tools is an irreplaceable way to learn things thoroughly. That said, HN readers from outside the Elixir should know there are great libraries for all of those use cases. Point in case is background job processors—we have plenty of options, though I’m especially fond of Oban[0] (full disclosure, I’m the author). [0] https://github.com/sorentwo/oban https://github.com/sorentwo/oban

princevegeta89 6y ago
I got into it before Oban was ever released. However, it seems like a solid solution. I've looked at Faktory as another great option as well: https://github.com/contribsys/faktory/ https://github.com/contribsys/faktory/
- dnautics 6y ago
  haha, yeah the annoying thing about elixir is that sometimes, you give up, roll your own solution (because it's not terribly hard to do), and then right after you're done, some team has built a slightly better solution (because it's not terribly hard to do).
AlchemistCamp 6y ago
> Rolling your own tools is an irreplaceable way to learn things thoroughly. I completely agree. It's also a great way to avoid complexity you don't need. There are limits, but especially while learning I like to err on the side of fewer dependencies. BTW, I just now saw that getoban.pro was a thing. It looks great!