Gradualizer VS emqx

Gradualizer is a typechecker for Erlang. It's a bidirectional typechecker, which means it uses non-local type inference, i.e. a blend of typechecking with type inference. It aims to follow the principles of gradual typing, so that it's possible to add type annotations only to parts of your code, instead of the entire code base, and it's going to work with that. One of the eqwalizer authors, Ilya Klyuchnikov, contributed to Gradualizer in the past.

If you're looking for compile-time (or actually check-time) feedback you might be interested in Gradient, a gradual type checker for Elixir and a frontend to Gradualizer. These tools, while experimental, allow for applying "making illegal states unrepresentable" principle thanks to exhaustiveness checking. In general, they are more akin to the ML-style type checking than Dialyzer is.

I'm hoping that https://github.com/josefs/Gradualizer and its Elixir counterpart get us closer to what "I" want. I find dialyzer often inscrutable compared to something like OCaml's or Haskell's type errors.

I do still use it and typespecs, because it's better than no checking.

There's Gradualyzer with support for Gradual Typing on the way.

There's an effort currently being led by Facebook to create gradual type system for Erlang call Gradualizer, which should also make its way over to Elixir.

https://github.com/josefs/Gradualizer

EMQX (optional): Open-source MQTT broker for IoT, IIoT, and connected vehicles. Used for managing your toys.

I do know a real world use for Erlang (it also surprised me when i investigated about it), but two of the biggest mqtt brokers are coded in erlang: emqx, vernemq

EMQX is a 10-year-old open-source project under Apache License 2.0, with 11k stars on GitHub（https://github.com/emqx/emqx), 20M downloads on DockerHub (https://hub.docker.com/r/emqx/emqx), and 400+ paid customers worldwide. The Sweden address you mentioned is only the registered address of our Sweden entity. We’re a globally distributed team. EMQX European R&D team members work remotely in Sweden, Germany, the UK, and Brazil. We have similar registered addresses for entities in Germany and the USA too. See my response in linkedin for the address doxing.

Hello, we’ve met situations where messages are accumulated in EMQX due to slow user consumption, and then EMQX will be killed by the operating system as it takes up too much memory. It is usually caused by improper configuration. However, we are unclear about what kind of situations you met. Could you please raise an issue in our GitHub community at: https://github.com/emqx/emqx/issues? Our experts will try to offer help asap.

EMQX is an open-source, highly scalable, and distributed MQTT messaging broker written in Erlang/OTP that can support millions of concurrent clients. As such, there is a need to persist and replicate various data among the cluster nodes. For example: MQTT topics and their subscribers, routing information, ACL rules, various configurations, and many more. Since its beginning, EMQX has used Mnesia as the database backend for such needs.

EMQX(https://github.com/emqx/emqx) is an open-source project under Apache License 2.0, we don't think there are national borders for open source. The nature of its being open-source means it is developed, tested, and used by the open-source community worldwide. For a popular open-source project that has been downloaded by 15M times and adopted so widely globally for many years, it’s impossible to have a backdoor hidden without being discovered.