eqwalizer VS three-tier-multithreaded-archit

I don't think the implementation itself is at fault, but yes, I do think that the design of dialyzer makes it an (at times) faulty type checker. The unfortunate reality of a type checker that fails sometimes is that it makes it mostly useless because you can never trust that it'll do the job.

To be clear, I've had it fail in a function where I've literally specced that very function to return a `binary` but I'm returning an `integer` in one of the cases. This is a very shallow context but it can still fail. Now add more functions, maybe one more `case`.

I think an entire rethink of type checking on the BEAM had to be done and that's why eqWalizer[0] was created and why Elixir is looking to add an actual sound, well-developed type checker. Gleam[1] I would assume is just a Hindley-Milner system so that's completely solid. `purerl`[2] is just PureScript for the BEAM so that's also Hindley-Milner, meaning it's solid. `purerl` has some performance issues caused by it compiling down to closures everywhere but if you can pay that cost it's actually pretty fantastic. With that said my bet for the best statically typed experience right now on the BEAM would be `gleam`.

0 - https://github.com/WhatsApp/eqwalizer

1 - https://gleam.run

2 - https://github.com/purerl/purerl

While it's not static-typing, compile-time type checking for Erlang have come a long way: Eqwalizer works pretty well - but I may be biased since my employer sponsors the project.

1. https://github.com/WhatsApp/eqwalizer

Note there is also research happening in this area by the Elixir team. The WhatsApp is also working on static types for Erlang, which I am certain will be available for Elixir too at some point.

From the discord blog posts it seems that elixir powers the chat system, with rust and python as the other two main languages in their stack.

As for whatsapp, they are mainly a erlang shop and yesterday they open sourced a type checker for erlang:

https://github.com/WhatsApp/eqwalizer

https://github.com/samsquire/three-tier-multithreaded-archit...

You could implement complicated interlocking workflows with this syntax, because you just need to wait for events as defined.

LMAX Disruptor gets some good requests per second

Thank you so much Python core developers and steering council. Python is one of my favourite languages along with Java and C.

I greatly welcome true multithreading in Python.

I use both multiprocessing and multithreading in Python. See [0] for my multiprocessing example and python Threads for IO heavy tasks in [1]. But it would be far more efficient to use true threads.

Threads can communicate any amount of data in a single atomic almost instant operation. Using the local loopback interface or multiprocessing or pipes, this is not possible.

I am working on a multithreading architecture I call three tier multithreading architecture

https://github.com/samsquire/three-tier-multithreaded-archit...

My goal is extremely scalable and performant servers but Python is probably the wrong job for that.

[0]: https://news.ycombinator.com/item?id=36897054 (my description of my use of multiprocessing)

* Lockfree Ringbuffers are used by CPU threads and lightweight threads to communicate.

I invite feedback and comments: https://github.com/samsquire/three-tier-multithreaded-archit...