England and America are two countries divided by a common language.
These words are attributed primarily to the playwright, George Bernard Shaw, although some claim that Oscar Wilde spoke them, instead. Never mind; let’s consider these substitutions:
Well, you get the idea. The idea that we try our best to use English in the worst possible ways. If we say something simply, then we must be simpletons, no?
When I studied philosophy as a sophomore at the University of Georgia far too many years ago, I read an author’s concept of how Immanuel Kant would have defined or described the experience of death. Thus:
Death is the finite determination of infinity which has further determined itself by its own negation.

The short version could be: “Death is the end of life.” English translations from German often result in stultifying constructs.
The same is often true for writings by programmers, bureaucrats, lawyers, and Chairmen of the Federal Reserve when they speak to lay people (us).
Consider this:
The Plain Language Action and Information Network (PLAIN) gives some very good examples of bad vs. good English usage. Consider these:
We know how to write, especially those baby boomers amongst us who, when we were high school students, were forced to undergo the torture known as “diagramming sentences.” (I reckon many would have gladly exchanged waterboarding for this exercise, inflicted upon us by sadistic teachers of the English language.) We understand that there is a distinct difference between the spoken and the written word. Why?
For most of us, if we our hearing is not impaired, we pick up on a speaker’s inflection and tone as well as the words she utters. When we speak, we use what can and must be called “conversational” language; we are much more tolerant of grammatical errors because there are multiple communication modes present.
When we write, our communication with others is two-dimensional at best. We pay more attention to the grammar than we do when listening or speaking. We do this because we need to eliminate confusion and misinterpretation as much as possible.
Good technical writing depends upon our use of plain language. We impress no one by adding words and modifiers or by loading our writing with “…ize” words or three- or four-letter abbreviations.
I submitted the final draft of a user’s manual to my boss several years ago. I was happy with it, but I expected some changes. However, my boss liked it, too, and returned it to me with but one change. He wanted me to change all instances of “to use” with the proper forms of “to utilize.”
Well, the use or misuse of “to utlize” is one of my major pet peeves.
Instead of showing my disdain, however, I said “Okay” and started to leave his office. As I opened the door, I turned and asked him, “Say, what does ‘utilize’ mean?”
Without looking up, he answered: “To use.”—pause here…a very pregnant pause—then, he uttered a word or two I do not here quote, and told me to disregard his change.