Hard to say without knowing more context, but they could have been right. Personally I'd prefer clearly named, domain-specific container objects with adequately named properties than having to deal with "anonymous" Tuples all over the codebase, and being forced to remember what the first element was, what the second one was etc.

What makes a container object domain-specific? If I just have to pass data through the application, the anonymity may be appropriate.

Wouldn't using a tuple in Java be like using inserting things into a Object[] and pulling them back out casting to the object you want to use?

What library was this?