Better code documentation? Static analysis? Compare to Erlang with typespecs and Dialyzer.
> You want Java you use Java.
Why Java? Why not SML, OCaml, Haskell, Rust? Those are statically typed languages, too.
> Oh it [Java] sucks? I wonder why...
Because it's statically typed yet it's dynamically typed ("Object" class thing)? Because its type system is quite primitive and somewhat inconsent? Because it was designed for use in TV sets two dozens years ago, and has barely advanced as a language since then? (No, foreach loops and lambdas don't qualify as a significant step, those are merely syntax sugar.)
> Oh even better, you set a type, does it prevent you from using things with a similar interface? Like iterables in place of lists?
Type specification signifies code author's intent. This is a very good thing, and I want to see it much more in the code. I don't expect type specs/hints to do anything more for a dynamically typed language.
Developers on those languages usually don't push for crap like the Java developers do
And I don't want to use Rust or Haskell where Python can solve the problem just fine. Overhead and development time is also a problem
Type hints add development time and bureaucracy. The 80 columns limit was supposed to be a guidance as well but now it has become almost mandatory
> [...] I don't want to use Rust or Haskell where Python can solve the problem just fine. Overhead and development time is also a problem
Yet you suggested using Java. Something in your comments seems inconsistent.
> Type hints add development time and bureaucracy.
That's why they are (going to be) optional. But for larger codebases beaurocracy adds some structure, which can be beneficial.
BTW, did you know that beaurocracy was an invention of ancient times? Yes, an invention. It allowed citizens to know what to do with their requests to authorities. Beaurocracy is generally a desired thing, it's excessive beaurocracy that is awful.
Only for those whose pinnacle of programming editors are from a VT-100 era.
Because thinking and reading the first phrase of PEP 8 is too hard, cargo culting is easier.
You want Java you use Java. Oh it sucks? I wonder why...
Oh even better, you set a type, does it prevent you from using things with a similar interface? Like iterables in place of lists?