It all depends on the context. In code that is not performance-sensitive, a bit of object churn isn't a problem. However, there are places where a lot of obje

It all depends on the context. In code that is not performance-sensitive, a bit of object churn isn't a problem. However, there are places where a lot of object churn can really be problematic. In particular, I find that Android applications tend to be somewhat sensitive to this. However, even in desktop or server applications, a lot of object churn in a tight loop can be bad.