On Thu, 21 Jul 2016 18:30:36 -0400, nospam wrote:
> you snipped the context and i don't remember what that was in response
> to.
Thank you for your astute advice.
Choosing the proper interleaved posting style is never perfect, but my
preferred trim-posting style is often termed reminder-trimming, and is
described in many Usenet etiquette texts.
It has advantages & disadvantages, but it's designed to be a point-by-point
bullet-item style response.
I think, but am not sure, RFC 1846 (aka son of 1036) might describe it more
fully.
"Posters SHOULD edit quoted context to trim it down to the minimum
necessary. Readability is enhanced if quoted text and new text are
separated by an empty line."
(Reference:
http://www.faqs.org/rfcs/rfc1849.html)
> your goal is to troll.
I never troll.
I simply respond to your points.
So we respectfully disagree that simply responding to your stated points is
trolling behavior.
>> She asked me to give her a one-to-one map of the best Android apps to the
>> best iOS apps.
> <
https://www.google.com>
We respectfully disagree on the best method of testing the one-to-one map
of the best Android and iOS freeware when migrating from Android
functionality to iOS functionality.
There are quite a few problems with picking free Android-to-iOS migration
apps simply by online reviews.
The biggest problem is that the reviews are biased.
The second biggest problem is that the reviews are intended to garner
sales. The third biggest problem is that the reviews don't review the
freeware as much as they review the payware (see first two points).
Since her two devices, as are all of mine, are 100% freeware by design,
most online software reviews don't cut the mustard.
In reality, the review process for freeware is expensive in terms of time,
so, since I have already expended that time to choose the best freeware in
existence, she can easily benefit from my wealth of experience.
>> Sometimes they are the same (e.g., CoPilot on iOS is essentially the same
>> as CoPilot on Android); but most of the time they're different.
>
> that part is true
There *are* marked differences between Alk CoPilot on iOS versus CoPilot on
Android which I've written about in gory detail in the past; but overall,
when an application is allowed on both platforms, it's "mostly" the same
functionality (e.g., VLC, Gmail, Sideline, 510 Scanner, Here Maps, MS
Office, etc.), the realitiy is that there is very little overlap in the
*best* freeware available on each platform.
For example, the best offline roadmap freeware has only CoPilot, Google
Maps, and Here.maps in common (Maps.Me not making the best list - but for
some people, you can add that too.) There is even less overlap (zero
overlap, in fact) for the best Android off-road trail-mapping freeware.
> since you lack the latter, that explains why you need to ask.
This is an interesting fact, in that the test process uses the same
functionality requirements but different software is essentially required
on each platform in order to find the best freeware (in fact, I'll post a
review of Here Maps on Android versus on iOS separately into the mapping
functionality thread).
>> So, since I've already done all that work,
>> and since I have more experience than most people do, she wanted to mine my
>> results.
>
> delusional.
I don't feel the need to insult you when I respond to your points.
In this case, I have a map of the best Android freeware versus the best iOS
freeware, but it's only visual.
All I'm trying to do is put that one-to-one map into a text file.
I can see the differences on my devices, both of which have the same
functionality requirements.
The software is essentially *different* between the two platforms.
Shockingly different.
That's because I choose the best freeware out there based on a strict set
of functionality requirements.
> which means it takes more than a split second.
To *generate* the raw list in both your example and mine takes,
essentially, a file-output or "ls" or "dir" command, all of which takes a
split second.
The iOS output requires extensive editing for actual productive use.
The Android output is good to go right from the start.
However, I'm an expert at editing, since my editors of choice all
incorporate regular expressions; so, for me, the extensive editing required
of the iOS output isn't as much of a drawback as it would be for many
others.
>> That archive is set to be on the external flash card.
>> So, I pop that external flash card into a computer and list to a file:
>> E:\sdcard1\data\software\apps\> dir > apps.txt
>
> even more time.
This is an interesting comment from you, which we covered in the iOS-users'
psychology thread.
What you do is "cherry pick" meaningless factoids, in order to make iOS
always come out on top - while I - being psychologically *different* than
you are - I am far more *balanced* than you are.
For example, as you must be aware (but conveniently forgot), you generally
connect your iOS device by USB cable to the iTunes computer. I do the same
on Android, and then I don't need to even pop out the flash card to access
the full directory contents of the Android device.
In addition, once we both have our output of the installed files, the
editing required of the iOS-iTunes-based output is extensive, whereas the
editing required of the Android output is minimal.
Furthermore, I have to *install* hundreds of megabytes of immensely
monolithic software to even think of using the suggested iTunes method -
which takes an immense amount of time because this unnecessary behemoth
then has to be painstakingly exterminated after the fact (yes, I know, you
feel iTunes doesn't leave useless vestiges of itself all over the place -
but the last time I uninstalled it, I was digging out unnecessary bonjour,
apple drivers, quicktime and other components of its avowed bloatware
littered all over the place - none of which went in the place Apple's very
own installer was told to put them in).
> that it takes a tiny fraction of a second to do for ios.
Except that it doesn't.
> you claim to have a mastery of the english language, yet you don't
> understand the actual words.
It's interesting that the iOS users' tendency to end all posts with an
insult extend beyond the *need* for the insults.
I am not insulting you.
In fact, I'm thanking you for your astute and helpful advice.
I will disagree with you on the finer points of the results - but I don't
feel the intense need to end every post with an insult.