The Comparable interface shows how it should be done.
(But on the other hand, if you were starting over it would be better to learn from Go's interfaces.)
This of course, only makes sense in the post-generic world of .net +2.0 so he does excuse their presence as a vestige of 1.1.
I dunno, I haven't actually watched this presentation so maybe I just need more context. But I've been programming in C# since it came out and not once have I ever had any real issues with Equals and all of its related methods.
As with the case of explicitly sealed/unsealed classes, it seems like Jon's MO is to make programmers think about some of these things more carefully rather than have a "correct 90% of the time" default; a sentiment which I can definitely appreciate. :)
Anyway, he discusses it at approximately the 36 minute mark. Well worth a look.
What are you saying - that if it was copied from Java, it must be OK? It is not impossible that object is both copied from Java and bloated.
I disagree on getting rid of Equals if for no other reason it's implicitly used often
But it isn't used often. Take an application of yours. What percentage of the types that you have defined in it need to worry about equality over and above ReferenceEquals? You may have collections of customer, but never collections of CustomerFactory, CustomerRepository, CustomerController, CustomerEditForm, etc...
And if there is no canonical idea of equality, that's what overriding Equals is for
If you override equals, you can only have one kind of non-reference equality per type, which is what Jon Skeet says is not always the right thing.
I disagree on getting rid of Equals if for no other reason it's implicitly used often (like in collections). And if there is no canonical idea of equality, that's what overriding Equals is for, and what Object.ReferenceEquals is for (return yourself to the base notion of equality when you need it).