But herein lies part of the problem - at first you said that the two meant the same thing in common parlance, then you said the same thing in technical parlance; there's confusion in the audience right there. Anyway, while it was clear what you
meant, what you
said was not quite correct, which is why I piped up.
Particularly in technical writing, you've got to get your words nailed down correctly. This is why there are things like the RFC defining what 'shall', 'should', and 'may' mean (intended for other RFCs, but it's also used elsewhere)[1], or the development of Simplified Technical English[2]. The latter was developed in aerospace engineering, where minor misunderstandings can literally cost lives.
Subtle differences between words are important, and they allow us to communicate more complex ideas. Twitter may have it's place, but any conversation involving nuance really isn't suited for it. A high-quality conversation includes caveats and careful framing, which can't really be fit into 140 characters. At least, in my opinion.
[1]https://www.ietf.org/rfc/rfc2119.txt
[2]http://en.wikipedia.org/wiki/Simplified_Technical_English