Static methods vs. instance methods

[vforvova]

Hi! Please explain why things have been done this way: in one hand we have Future with method fork for instance, in other we have Either with static method either?
It would be more comfortable to use them in the same way. Would it be better to have both an instance and static methods for them?

[CrossEye]

Anyone with a good answer to this? @asaf-romano? @buzzdecafe? @davidchambers? @scott-christopher? @TheLudd? Beuller?

[scott-christopher]

My take on this is if the method is unique to the instance (such as fork in the case of Future), or a fantasy-land method then they'll end up attached to the instance. If the function can be created external to the instance it will exist as a static function. I'm sure there have been some arbitrary choices made over time and it would be good to get them all cleaned up and consistent.

I'd personally be happy for the library to provide both static and instance methods where possible and would welcome a PR (assuming no concerns are raised from the others).