Small nit: Currently Elixir pushes users to call Erlang when working with crypto. This > doesn't align with Elixirs goal of developer productivity.
I've always found the ability to dip into erlang a major factor of Elixir's promise of developer productivity. :D I agree with the sentiment that the experience could be much improved, both by contributing to OTP, as well as perhaps creating a higher-level Elixir swiss army knife geared towards common applications of erlang's modules. I wanted to contribute a point alluded to here but not directly stated: a major virtue of a vogue or standard crypto library living outside core is that vulnerabilities can be patched and deployed infinitely faster that the language itself. This agility is a commonly stated motive to have feature proposals be implemented outside of the language instead, but crypto seems a particularly compelling domain in which to prioritize that responsiveness. I am willing to help maintain it. But I definitely can't do this all by > myself so I'm looking for support. I wish I could be of more help but I'd be useful as a maintenance triager only, it's beyond my realm of expertise. But I recommend making a post on the forums, perhaps to funnel interested parties into a dedicated #crypto channel on slack? I can see a lot of people there being interested in contributing. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/50d04abe-cb36-458b-82db-65adf67b7a81%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
