From: Tony Cooper <>
Subject: Re: Windows 10. Horrible!
Full headers:
From: Tony Cooper <>
Subject: Re: Windows 10. Horrible!
Date: Mon, 30 Oct 2017 13:30:37 -0400
Lines: 29
Message-ID: <>
References: <> <5ipjce-a7m.ln1@Telcontar.valinor> <ot7i7g$oo$> <> <301020171310042656%nospam@nospam.invalid>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: JGthiArZUHd2oR+xNiaYngu04o3cZe0DNmTj6CtWxaQSfYMf0x
Cancel-Lock: sha1:31vtkT4yG+t7N2NR3EX82nH6kv4=
User-Agent: ForteAgent/
Print Article
Forward Article
On Mon, 30 Oct 2017 13:10:04 -0400, nospam<nospam@nospam.invalid>

>In article<>, Tony Cooper
><> wrote:
>> Any new version of any software requires a get acquainted approach
>> that most of us are able to successfully negotiate in a short period
>> of time.
>for some new versions, that's true, but definitely not all of them. 
>many times, the changes are minor or even entirely internal, resulting
>in no need to 'get acquainted' whatsoever.

Those are not "new versions".  I know you have a vocabulary
deficiency, but a "new version" is different from a new release that
makes changes "under the hood" in the same version.

A "minor" change does not mean a change that doesn't require an
adjustment on the part of the user to understand the change.  Changing
the name of a tool, but not the tool, would be a minor change.  The
user may need to get acquainted with the new term.

>once again, you're wrong.

You'd like to think so.
Tony Cooper - Orlando, Florida