1) In general, if all things are equal, your first statement is true. I just ignore that part because anyone has ever seriously code something in their life for a living would come to that conclusion, one way or another. I just don't bother to argue about something outside of my issues when I ask for people's opinion on something else.
2) You read too much and assume too much in one single line. My statement , quoted by you, applies equally to all products but your assumption (your preconception and bias?) carries it into your own world. Labview could elegantly works and LabWindows could be a stuff pig or vice versa. It all depends on how it fits into our needs and the cost associates with the product ie. learning curve, ability to incorporate with other 3rd party codes etc. With ZERO understanding in our organization, our strength, weakness and our needs, you have already bloat some strong opinions based on your assumption. Of course, with a strong background in C & C++ programming language and environment, we are definitely bias toward applying our strength in such environment, especially those with math intensive codes. However, we also have a short term turn around cycle for quite a few products, which I wonder whether Labview could fit nicely or not. With my understanding of our organization, I have to make a compromise somewhere to have a single platform, so yes, we do use hammer for everything, provided 80+% of our job is involved with nail. The rest of those things can be flat a bit but that's the penalty we have to accept.