Why use tuples instead of objects?

Question

The codebase where I work has an object called Pair where A and B are the types of the first and second values in the Pair. I find this object to be offensive, because it g

Answer 1

This is just prototype-quality code that likely was smashed together and has never been refactored. Not fixing it is just laziness.

The real use for tuples is for generic functionality that really doesn't care what the component parts are, but just operates at the tuple level.