4 ms·
Types are for the compiler. Not humans. We just happen to use it as a way to remind us what data looks like. It's not the only way to figure out what happens in
by beders 8y ago
Types are for the compiler. Not humans.
We just happen to use it as a way to remind us what data looks like.
It's not the only way to figure out what happens in a function.
I've gone the exact opposite route now: From static types to dynamic types to interactive coding using specs.
Specs are much more expressive than types but - and that is the main difference - it's a la carte and opt-in.
If you don't opt-in, you'll spend more time at the REPL figuring out what a certain piece of code does.