Well, as others have pointed out, there is a very, very small number
of uses for which the push notification is not appropriate. However,
as I said before, they've solved the vast majority of issues this
way. I don't think we exactly disagree, but I think that the number
of users who will actually be impacted by the limitations is extremely
small, and that even for a lot of those who will be impacted, the pros
will outweigh the cons. What I'm try towork through are the
misconceptions, like Will Lomas put forth, that you can't move back
and forth between multiple apps and essentially multi-task, and that
point has been lost in an argument about technicalities that will
effect less than a single percent of users. LOL. Your battery issue is
likewise the same. It will impact a very, very tiny number of users.
That doesn't mean the problem doesn't exist, but seeing it harped on
about and latched onto by the nay sayers as an excuse to downplay the
iPhone's advantages is frustrating.
I hope this makes sense. I have never said, and would never say, that
any device is perfect for everyone. I think the iPhone is more than
adequate, and is in fact ideal, for a huge numbe rof users, and that
by arguing things like this multi-tasking situation, you're confusing
folks like Will Lomas who would be just fine with an iPhone, but think
they won't because of complaints about SSH and IRC.
Hope that makes more sense. :)
Josh de Lioncourt
…my other mail provider is an owl…
Twitter: http://twitter.com/Lioncourt
Music: http://stage19music.com
Mac-cessibility: http://www.Lioncourt.com
Blog: http://lioncourtsmusings.blogspot.com
GoodReads: http://goodreads.com/Lioncourt
On Jul 14, 2009, at 7:43 PM, Scott Bresnahan wrote:
>
> Hi, Josh,
>
> Take a closer look at what is possible via push in the APIs and you
> may be surprised at how limiting it is. Your argument about Apple
> solving the problem by introducing push is more marketing hype than
> fact. At the core, you can't keep sockets open in the background
> which many RFC standards like irc, ssh, telnet etc depend. Apple's
> answer is well, rewrite the standard. That's not an answer. you
> cant' just rewrite every server platform out there to support Apple's
> whim of of a lame push notification method. If you're starting from
> scratch today, writing a new client and server platform, then sure,
> you can work around it. But there are a lot of pre existing
> technologies that won't work no matter how the app is coded simply
> because the problem is not with the client but the server piece the
> client is meant to communicate with. But again, this isn't a problem
> for most people, but only for those who need to multitask, like
> keeping multiple sessions open at a time.
>
> As for batteries, I agree that *most* people don't' have spare
> batteries. However, just because you haven't met them doesn't mean
> they don't exist. I had two spares back when I had an analog
> StarTac, and I know a small fraction of people who still have spare
> batteries for their phones today. Granted, these folks tend to like
> Star Trek the original series vs tng, but I digress.... not to
> mention I think they try to use their phones as laptops, but who am I
> to argue their inefficiency. :)
> .
>
> I can't believe I'm arguing the devils advocate on this..... did I
> mention I love my iPhone? But, it just doesn't do windows, so stop
> pretending it does. lol
>
>
> --Scott
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/macvisionaries?hl=en
-~----------~----~----~----~------~----~------~--~---
