> Why don't you voice your opinion and for gods sake stop just sitting there
> reading what we post?
> Get your role right and show us you have some leadership to the crew(us
> developers).
> If anyone is going to make it happen, its this community of developers.

> The more silent you remain, its in human nature to trust less.   IMHO,
> you're bordering to recover!

> George

> On Thu, Jul 17, 2008 at 9:58 PM, Shane Isbell <shane.isb...@gmail.com>
> wrote:

> > The next time Google comes out with some big project asking for developer
> > support and talking about openness, we will know not to trust them. Time to
> > move on.

> > Shane

> > On Thu, Jul 17, 2008 at 11:40 AM, Jon Webb <jonaw...@gmail.com> wrote:

> >> This explains something I've wondered about for a while. Back before
> >> the competition I tried to build an app and couldn't get basic things
> >> (like reading past byte 16384 of a file) working. I reported a bug,
> >> provided an example, the whole thing. The bug and a lot (like
> >> hundreds) of other bug reports were reviewed. But then they were never
> >> fixed. Couldn't finish the app. Fine, whatever, I'll wait for the
> >> phone.
> >> I thought it was odd there were no further SDK updates -- what was
> >> going on? Was Android delayed or canceled? Were they trying to make a
> >> really good, complete release before they came out with something?
> >> Now I know. They decided to work closely with a few developers and to
> >> give them an advantage over everyone else. Could be there's a
> >> reciprocal agreement with those developers to give them better support
> >> in exchange for their app development work.
> >> It's not an unusual move in software development. Not particularly
> >> nice not to make it public, though. Just leaves the rest of us
> >> hanging, waiting for an SDK update that never comes.

> >> On Jul 15, 9:57 am, Hong <lordh...@gmail.com> wrote:
> >> > just trying to get the rest of us excited... that Android still has some
> >> > progress...