Suppose you have a generic key-value store. If a value is not present, the lookup returns null. You use it for a cache that maps user IDs to phone numbers. Some people don't have phone numbers, i.e. their phone number is null. But now you can't represent that in your cache. (JS "fixes" this -- if you want to call it that -- by using a second type of null: undefined.)
Option is generic and can applied arbitrarily deep; null/Nullable is a sentinel that can be used once.
Option is arbitrarily composable, and the superior choice.
Option/Maybe can represent arbitrary optionality, while null is limited to a sentinel value.
I wrote a blog post about null (https://www.lucidchart.com/techblog/2015/08/31/the-worst-mis...) and this one of the examples:
Suppose you have a generic key-value store. If a value is not present, the lookup returns null. You use it for a cache that maps user IDs to phone numbers. Some people don't have phone numbers, i.e. their phone number is null. But now you can't represent that in your cache. (JS "fixes" this -- if you want to call it that -- by using a second type of null: undefined.)
Option is generic and can applied arbitrarily deep; null/Nullable is a sentinel that can be used once.
Option is arbitrarily composable, and the superior choice.