> Out variables are really great when working with existing code that predates Tuples (for example, the entire BCL). We don't just introduce language features t

> Out variables are really great when working with existing code that predates Tuples (for example, the entire BCL). We don't just introduce language features that will only work well for new code. We also want to make the experience of coding against existing APIs feel better. I disagree on this point. If there is a language feature that has been superseded by a better alternative, continuing to add sugar to the old feature only serves to perpetuate its use. It embiggens the language while providing relatively little value in return. Furthermore, it adds confusion as to what should be considered idiomatic. Tuples and deconstruction are so clearly better than out variables, I would have thought it would make more sense to deprecate the "out" feature entirely. Or, at the very least, not make it easier to use them. Awkward and outdated features should be painful to use. I also felt that this was a very odd addition. Even odder, the article doesn't even list tuples and deconstruction first.