Tony Morris

Dear #scala I wrote scala.Either in 2008. I wrote scalaz.\/ in 2013. Please stop using scala.Either. There are reasons.

@dibblego And I wrote org.scalautils.Or in 2013, to show we can have both good types *and* good names in #scala http://www.scalautils.org/user_guide/OrAndEvery …

@bvenners Identifier name reasoning is morally obnoxious and I will not be a part of it. http://dl.dropbox.com/u/7810909/media/doc/parametricity.pdf …

@dibblego How about identifier name *remembering*? Can't "relevant" names help people remember meaning once they understand the types?

@bvenners Yes and \/ is quite well established to denote logical disjunction.

@dibblego That's true about \/, maybe not so much about \/-, -\/, <<?, :?>>, |||, +++, and @\?/. Hard for users to remember all of them.

@bvenners @dibblego Anecdotally, \/, \/-, and -\/ are all well understood by a team I work with of 20+. Some of those others, not so much.

@mpilquist @bvenners ||| is established unlike "orElse" which has ambiguous meaning in scala. The naming obsession is way out of control.