@ado

My fear is that this type hinting pushes #python down the same bad road as #cpp:

Making an originally nice programming language more and more complex and ugly by giving in to the pressure of adding more and more features which don't fit into the original idea of the programming language.

In my view, the core philosophy of #python is that it is a high-level dynamically typed language . And the core philosophy of #cpp is that it is a low-level statically typed language.

Don't mix that.

@folkerschamel @ado Python's guiding principles are actually well defined. Nice easter egg to find them:

```
>>> import this
```

@kfet @ado

Doesn't type hinting violate the third and seventh zen?😔

@folkerschamel @ado Or if you mean the presence of type hinting at all, then it gets into a more interesting conversation with conflicting zens.

Practically speaking it is an incredibly useful feature for larger code bases, which is also kept entirely optional.

@kfet @ado

Yes, I think the type hinting at all was a bad idea.😉

I heared some arguments and experiences about the usefulness, but I don't see it yet.

The argument "it is optional" is the typical reason for giving up a sweat nice design and creating big messy bloated system instead.😉 A feature should not only be optional, but really useful and necessary to offset the inherent disadvantage of every new feature of making a system more complex.🙂

@folkerschamel @kfet @ado You will definitely see the usefulness of type annotations when you ever have to work on a large codebase project without them.

@tikhonov_a @kfet @ado

https://mastodon.social/@folkerschamel/110865468734887116

Possibly our codebase is not large enough 😔

But as serious comment, I would guess that mypy would get panic attacks when running on our code, because so many architectures are inherently based on dynamic typing.😁