While syntactic clutter, using options also means you're less likely to accidentally blow up your application. Having to call "get" is a little stronger a reminder that a given proc may not exist and you may run into nil-access-defects which will crash and burn down your entire application. Thus I _always_ tend to use Option to express something does not exist, never nil. I've had enough of nil checks for ref-types from my time in java.
That kind of safety I'd value more than the syntactic niceness of isNil.
