One issue with this model of learning Elixir is that you won’t necessarily learn about working on the BEAM. Ruby doesn’t allow for the same kind of development and architecture that you use on the BEAM, so there is a whole world of things out there that you might not learn about when doing this.
For sequential code that has a one to one mapping to other libraries on other platforms, I agree that it’s good to pick something you know from elsewhere and implement it, but it won’t introduce the concepts and thinking that are specific to platforms like the BEAM.
If you have something made in Smalltalk and want to implement the architecture from there that might actually transfer much better, but I doubt that applies to a lot of people.
