For example, if you're reading records from a SQL database, you don't have to bother wrestling with the type system – just tell it what your data looks like! :)
let Pet = Object.of({ name: String, happiness: Number })
$assume `fetchPets : (Number) => Promise( Array(Pet) )`
function fetchPets (minHappiness) {
return db('pets').select('*').where('happiness', '>', minHappiness)
}That feeling when even C++ is less verbose than Java ... another "lambda" feature.
Just the physical eye movement and scrolling is wasting time and energy on pointless things.
Python doesn't have types at all and it reads like pseudocode. This is not arguing against types - having types is valuable in the bigger picture - at interface declaration/global scope - but at local scope it's implied in the context and if you need help figuring some specific out you can just use IDE (you can't argue "that makes you depend on a IDE" - verbosity like Java makes IDE and code generation a requirement for productivity - this just makes it a nice to have tool)
I hear Java devs argue in favor of using static types because the type checking and IDE autocomplete lets them write code faster.
Dynamically typed languages are great because you don't have to write as much code to provide comparable functionality. The best quality code that's also the easiest to maintain is the code you don't have to write to begin with.
I used to contribute to an OSS library for parsing raw network frames into structured protocol data. 50%-60% of the code was type coercion and design pattern boilerplate to work around the type system.
I saw similar networking code written in JS and was in awe at how little code it took to accomplish the same. It was easily an order of magnitude less code.
Types are good for handling some edge cases. When types are required by default, it just adds a ton of unnecessary noise.
If it's not a script task or glue code I prefer static typing.
Java is just a very bad implementation of static typing, it's intentionally dumbed down and limited so that you don't need to learn a lot to understand code - and this results in weak type guarantees, bloated and tedious code base and silly patterns to work arround language limitations.
C# is a much better example of a productive statically typed language in the same family, F# is even better - those are just the ones I have experience with. I would have much rather done that blender project in F# over Python if I could (sadly only python API available)
Besides even dynamic language authors are seeing value in providing static typing with the recent trend of optional/gradual typing for most dynamic languages.