Well, I don't want to use the No Break attribute that can get accidentally blown out when I remove overrides, which I do all the time - it's a pretty crucial step. (I also make extensive use of character styling for other purposes, so I'd have to experiment with it for a while before I started using No Break in a char style.)
However, I have to plan for the future; most of the documents we produce will be revised and reused extensively. So, if I use a nonbreaking space in some FLRR text, I'm almost guaranteed to see it in print within the next three years, with the text fully justified and my nonbreaking space sticking out like a sore thumb.
BUT, if I just give up and use a soft return, I'm just as likely to see a poorly-placed line break. (I haven't yet spotted a nonbreaking space-related-problem like this, but I have encountered poorly-thought-out soft return usage from my past coming back to haunt me. Given how long I've been using the non-breaking space, I should see some poor justification based on its use any week now.)
So, is this worth a feature request: "Please make the nonbreaking space act like a space?" Or is there a typographical or technological reason for this behavior? The width of the space character is determined by the font, but can be altered by many other criteria, such as justification, tracking, horizontal scale, etc. Obviously, it's possible to make the ordinary space change width on the fly along with justification. It would make sense to me that the nonbreaking space would be affected by tracking and horizontal scale, and my quick experiments show that it is. So, why isn't it affected by justification?