It’s definitely a thing in our industry! I used to work on a team with a few people who questioned things heavily. It was great! One developer would literally question every single feature request that would come through product. “Why are the users asking for this? Is there a way we could solve this problem by doing nothing at all? Would they be able to use an existing feature if we slightly altered it?” This lead us to start doing really quick prototypes so the customers could play around with their idea. Often they actually wouldn’t want the feature once they actually tried it. All parties were much happier.

The problem being solved, if you watch the https://www.youtube.com/watch?v=Jf5Hsa1KOc8 is lack and quality of tooling that typed languages have.

Who needs this tooling? First of all beginners, this should speed up adoption of the language.

Is this a good thing? I would say yes and no, yes because there will be more elixir jobs and no because the community will degrade and become fragmented like it always happens with popular languages.

Just to be clear I support the type checking system. I also think the work going into this language is top shelf and high quality and the work others have done is worthy of their time.

For me this question was way more abstract than just talking about if the type system was a worthy problem to be solved.

At the root of the question is the question “why”.

The “Why are we doing x, y or z?”

I won’t argue if the type system is a real problem or not because its not really for me to say,
but the fact someone is asking that question gives me confidence we are at least on the right path.