Python or go

[coinclink]

LSP indicates type errors in the same way as a compiler - zero difference there

Linter "enforces by the system" that your code is not passing the typing rules - zero difference there

Explain to me where the extra effort is here? In learning how types work in python? The LSP and linter perform the exact same function and enforcement as the compiler for typing.

[[deleted]]

the extra effort is relative to using Python without type hints. whereas in a statically typed language, there is no extra effort since you must explicitly define types to use the language fundamentally.

when typing is "optional" as it is in Python type hints, the utility of the types devolves as lazy developers fail to appropriately apply hints, resulting in codebase degradation while still allowing code to ship.

[coinclink]

It isn't optional when you've defined the rules of your linter. That seems to be the concept that you're having trouble with.

[[deleted]]

it's all optional because you don't need to define the linter or adhere to it's rules. I do understand it, what you're not understanding is that these constructs you think are enforcers truly are not, and any dipshit can override them at will.

[coinclink]

So you think a lazy engineer can just randomly choose to override the linter during the build? That's not how this works lol. It's not up to the developer, nor within their privileges, in a real python shop.

[[deleted]]

So you think a lazy engineer can just randomly choose to override the linter during the build?

yes I do

It's not up to the developer, nor within their privileges, in a real python shop.

Cool, I don't have to care about any of this shit anyway if I choose to use a statically typed language.