 Elixir is a kind of different take on Erlang I would say, but where you know what the inventor of Elixir was trying to do was bring the power of Erlang to a lot of communities out there. I think from our end we'd mainly focus, you know from from an Erlang perspective we'd mainly focused on you know back-end distributed systems and embedded systems. What Jose Valin tried to do was you know how do you bring the power of Erlang and the beam to other communities and he did it by you know focusing on tooling so looking at tooling which which were which was more common in say front-end development. He was he looked at so you know you find tooling similar to what you'd find when you work with any of the JavaScript frameworks, Node.js or Ruby. It is also you know there's also different approach, developed approach which is maybe more suited to front-end development, mobile app development which is a top-down approach. In the Erlang world we've always used the bottom-up approach and again this is more because of types of problems we're used to solve. We're used to solving them and you know there there's a package manager again which I think sat at the core of Elixir. I think it was one of the very first you know projects which Jose kicked off was working on Elixir and which again gives you a large set of libraries and applications which you can just embed into your program and download on demand as needed. So I think those are the major differences. Together with the Ruby syntax which you know you don't have in Erlang. Erlang has a prologue like syntax so yeah.