I had someone say to me they preferred strict type checking in a Python linter over a statically typed language because they "don't like a build step"...
Dudes it's literally just worse compilation with extra steps.
I had someone say to me they preferred strict type checking in a Python linter over a statically typed language because they "don't like a build step"...
Dudes it's literally just worse compilation with extra steps.
I'm in favor of partitioning the set of reasons it can fail to compile into separate checks with separate tools. Taming the zoo of tooling is extra work, but smaller more focused tools are easier to work with once you understand their relationship to their neighbors.
There's a world of difference between:
> I've been using a different type checker and I like it, you should try it
And
> I'd like to switch our project to a different compiler
The former makes for more nimble ecosystem.
Yes, if you are stuck with Python something is certainly better than nothing. But we shouldn't be writing large production apps in it in the first place.
Should we be writing large apps at all?
I don't know how to respond to this. Yes, large software projects do in fact exist...