Another quick intervention: for those wondering why types and how they would impact Elixir, I have talked about this during my ElixirConf EU keynote 2022.
Also let’s please avoid categorizing people who prefer static or dynamic as X or Y. Calling part of the community noisy or trendy sounds very condescending and unproductive (it is also condescending towards Elixir maintainers, as it implies we are doing nothing more than following trends).
As someone casually following Elixir from afar (I read the Phoenix book and worked through a Dave Thomas course), I’m concerned the type system won’t be good enough (for me).
For comparison, I found the efforts to introduce typing in Ruby (sorbet, RBS) rather underwhelming and not very useful in practice.
From my point of view, a type system can be a great modeling tool, and offer a lot of garanties.
And I like constraints. As with any tool it can become a nuisance if badly used of course.
Please check out OCaml for ideas on how powerful and ergonomic a type system could be
I’m concerned that it’s operating over AST, which I don’t think is a good strategy. I tried this and gave up on it for a reason (also someone else in the community did too). Also, I’m concerned that the sets are not principled. They run the risk of being just bags of types that got chosen because of arbitrary reasons of the developer. Principled sets should be tied to some equivalence class that isn’t up to the implementer of the type system.
I’m considering returning to work on Mavis/selectrix which I had suspended since the proposed type system has these properties
I’m worried we will not get enough benefit from all the extra typing we will have to do.
Soundness is also important for me, otherwise it ends up like TS where all your code says this thing is a banana but in runtime it blows up because it is actually an orange.
So you mean the replies in this thread have to conform to a certain type of comment?
Sorry, couldn’t resist. 
I’m gonna 180 the people that say they fear it will be mandatory:
My biggest concern is it being optional, and the developer experience being vastly different between dependencies. Some libraries I use will have types and the associated completions/lints/… and others won’t, meaning I will have an inconsistent experience using them.
How productive/practical it is to use and whether or not it inadvertently diminishes the use of primitive data structures in favor of complex typed data structures.
Typed languages have this tendency to introduce unnecessary data structures to account for intermediary transforms.
Programming is almost always a data transformation problem, and this is where Elixir shines: simple data structures and tools to transform them effectively 
I worry that the type system will make the code bloated and ugly.
If I want a dynamic language, I choose Ruby; Otherwise I choose Golang, I don’t choose Typescript as a mixture.
Making big changes to a language more than a decade after its launch can break habits, which is why I switched to Ruby after Golang added generics. I hate the ugliness of Typescript and like the simplicity of Javascript.