Which kind of reactive programming are you asking about?
If you are referring to the the Reactive Programming as in the Reactive Manifesto, the manifesto is seen by many as mostly a marketing spin on patterns that Erlang and the Erlang VM have been doing for almost 3 decades. And Elixir inherits all of that. For example, you use supervisors for resiliency, Erlang’s preemptive processes allows us to better predict latency and therefore responsiveness, etc. Even when we look at key aspects, such as being as event-driven, in Erlang/Elixir is part an integral part of the language and of the runtime via message passing, instead of something bolt on top.
However, if you are referring to the reactive programming related to data flows, as seen in Excel spreadsheets or language like Elm, Elixir has limited supported. Projects like GenStage and Flow are starting to explore such areas but there is a lot more to learn and work on.
