{"id":936,"date":"2010-06-11T11:38:50","date_gmt":"2010-06-11T10:38:50","guid":{"rendered":"https:\/\/blogs.mentor.com\/colinwalls\/?p=936"},"modified":"2026-03-26T16:32:35","modified_gmt":"2026-03-26T20:32:35","slug":"uniquely-annoying","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/embedded-software\/2010\/06\/11\/uniquely-annoying\/","title":{"rendered":"Uniquely annoying"},"content":{"rendered":"<p>As regular readers of this blog will know, I am very interested in languages and communication. I do not really speak any foreign language [although I have plans to brush up my Italian], so my main focus is English. I do my best to understand and utilize my mother tongue as well as I can.<\/p>\n<p>I am not a language purist &#8211; I readily accept that languages evolve over time and adapt to the place where they are being used. For example, I have no problem with American English, which many Brits feel is a corrupt form of the Queen&#8217;s English. It is not; it is simply a local dialect [which happens to be spoken by more people that there are English inhabitants]. I do not have a problem with language evolution over time &#8211; words change their meaning as society changes. However, I do get upset when such changes are as a result of ignorance and threaten to damage the language and inhibit our communication &#8230;<!--more--><\/p>\n<p>When I first visited the US, nearly 25 years ago, I was struck by the odd use of the word &#8220;momentarily&#8221;. People would say &#8220;I will be with you momentarily&#8221;. This literally meant that they would be with me <strong>for<\/strong> a short time. What they actually meant was that they would be with me after a short delay &#8211; <strong>in<\/strong> a short time. I saw this as a corruption of the meaning of the word, but not one that was particularly damaging, as ambiguity was unlikely. I observe that nowadays, even in an English dictionary, both meanings are listed. The language has evolved.<\/p>\n<p>Some changes, however, are unwelcome. I am so tired of hearing [on both sides of the Pond] people or things described as &#8220;very unique&#8221;. This is meaningless. It is like referring to someone as &#8220;slightly pregnant&#8221; or &#8220;a little bit dead&#8221;. Something is unique or it is not; there are no half measures. I would just about accept &#8220;almost&#8221; unique. If there are just 2 identical objects, the loss of one would render the other unique, so I suppose they are both <em>almost <\/em>unique.<\/p>\n<p>What people mean by &#8220;very unique&#8221; is &#8220;extremely unusual&#8221;, which is not the same thing at all. The reason why I am so resistant to this change is that the word &#8220;unique&#8221; has no really good simile. So, if its meaning is changed, we will have no clean way express the concept of uniqueness. Maybe we would need to steal a word from some other language. Any suggestions?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As regular readers of this blog will know, I am very interested in languages and communication. I do not really&#8230;<\/p>\n","protected":false},"author":71677,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[302],"industry":[],"product":[],"coauthors":[],"class_list":["post-936","post","type-post","status-publish","format-standard","hentry","category-news","tag-off-topic"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/posts\/936","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/users\/71677"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/comments?post=936"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/posts\/936\/revisions"}],"predecessor-version":[{"id":9862,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/posts\/936\/revisions\/9862"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/media?parent=936"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/categories?post=936"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/tags?post=936"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/industry?post=936"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/product?post=936"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/embedded-software\/wp-json\/wp\/v2\/coauthors?post=936"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}