@kevinb9n I like this framing a lot. It makes it all the more depressing that the replacement for `a == b` sometimes isn't `a.equals(b)` but rather `Objects.equals(a, b)`. Neither `a == b` nor `a.equals(b)` is a no-brainier!
@jessewilson How significant is interface vs. abstract classes in the age of default method implementations in interfaces? I do kind of like that abstract classes let you make the methods `protected`.
@geekinasuit I would love for us to make a habit of publishing these -- or even just keep going back and publishing old ones. I just don't know of many good sources for these kinds of discussions.
@geekinasuit Removing named() was a trade-off for sure. Anyone interested in some light reading on the topic can have a look at https://t.co/rq4CfJG4Ki
@geekinasuit Understood. And thank you, of course, for getting the ball rolling! I was just telling someone internally how I came to see the potential for Truth only over time, starting with "nicer than putting the expected value first" and exploding from there.
@foobarjet@googletesting Thanks! And thank you for bringing up automatic migration. We have some tools internally but should really publish them externally. We don't seem to have a bug file to track that, so I've filed https://t.co/Sb2Pcq2WjA.