Elixir is a relatively new programming language. It’s young functional programming language but very perspective. Elixir has been trusted by several companies and we are not exception. Today we are going to show you 5 reasons to take Elixir into account if you haven’t done that already.
It can happen sometimes that you work with Elixir and then you want to benchmark something. So, what will you use? We have a hint for you. Benchee is a library for micro benchmarking in Elixir that allows you to compare the performance of different pieces of code at a glance.
Despite, there’s not much projects in Elixir nowadays developed in Ukraine, we believe that Elixir’s features will make it very popular soon. That’s why we seriously considering the practical use of Elixir for JS developers and for Rubyists. One of the main reasons for that is Elixir concurrency. And today we are going to explore with you the Elixir Concurrency example and put it in practice. Are you ready?
If you didn’t hear anything about using Elixir and Phoenix for building extremely high performance and low maintenance system, we are here to help you. Even more, we can tell you about something new! Meet Phoenix LiveView! It enables rich, real-time user experiences with server-rendered HTML.
You can trust us when it comes to the topic of Elixir. We absolute fans of it. Let’s introduce you the new tool. Broadway is a concurrent and multi-stage data ingestion and data processing with Elixir.
Only the laziest one will not explore Elixir these days. This language is perspective and hard to learn, so it is even more magnetic for the newcomers to start. Elixir has several mechanisms that allow us to write expressive and intuitive code. But do you know what are Protocols in Elixir? Today we will tell you the whole truth about it.
A Supervision Tree in Elixir has quite a number of parallels to how developers using React think about a component tree. In this article, we will attempt to describe parallel concepts between the two – Elixir Supervision Trees vs. React Component Trees.