I've realised that I have a much better understanding of the semantics of languages that are value oriented. You avoid murky questions like this:
try:
raise Exception('')
except:
return 1
finally:
return 2
There's no 'right' answer here when choosing how a PL should work.
Related Posts
Playing with optional type signatures in Python, I realise that the return type is the most important to me.
I'd much rather have a function with only a return type instead of a function with only parameter types. It's often quick to add too.
I've been experimenting with different pagination UIs.
It's so common to have arrows, but I've realised they're redundant here. When you have the adjacent values as well as the final value, you don't need > and >> arrows too.
Thoughts?
I've heard of 'blub languages', where you don't realise that other languages have better abstractions until you've experienced them.
I think the same thing happens with individual features. I've seen several C++ folks miss variadic generics in Rust, but I've not written enough C++ to feel it.