From the point of view of a (relative to you) dumb user of a nexus
one, I'd be glad to add a bit to the disscusion.
I'm running android 2.2 froyo on a nexus one, and i'm loving it. No
other phone comes completely unlocked, allows tethering and a huge app
catalog while not being on any carriers
On Tue, Jun 15, 2010 at 7:08 AM, Zigurd zigurd.medni...@gmail.com wrote:
It looks like Google has about 7 people working on bug fixing plus a
few other engineers with assigned issues. So it looks like there is no
resource imbalance.
For what it's worth, all engineers work on bug fixing (and
Be a good fella', with 16 years in S/W development you can help
everyone and contribute to the development tools.
Android on the other hand is quite bug free, the developer tools have
some minor/medium bugs. And I bet your software is as buggy as Android
itself, if not more.
On 7 июн, 20:50,
Android issue tracking is in the open, so the numbers are available to
anyone:
There have been a bit over 9000 issues reported. about 600 released
(fixed and shipped) and 600 for future release. It's hard to
characterize all combinations of issue type and status. For example,
there are 8
Actually, I've been using BSD sockets since about 1992 with about 10
OSes :)
The bug I mentioned is not a 'timeout', it is for connection refused
which (as you know) should return immediately (network permitting)
with a 'connection refused' error. With Android the socket read is
sitting there for
I am agree with Hermo. Considering Android is fast growing project, that is
a quite bug-free project. Actually, there is no bug-free software in the
world.
On Tue, Jun 8, 2010 at 1:49 PM, hermo hermanag...@gmail.com wrote:
I think I'll rather live with some bugs in the SDK than do without
it.
I would guess that at most there is 10 to 15 maybe less Google
employees in this Android team.
Sorry, but you have no clue about this.
Well do we have to push you far to have a sneak peak of what is really
going on inside google's quarters :D
Don't be sorry, you are right I had no clue,
Also, we have been accepting an increasing number of patches from the
community. I have regularly been reviewing and accepting multiple patches
every week, as have other framework engineers.
Ok, i'm no C or C++ developper so I can't help you here...
BUT ...
Where is the git module and
I think I'll rather live with some bugs in the SDK than do without
it. Overall I think its very good and productive. I also appreciate
the fact that it includes features that might be seen as prototypes;
I'm a developer I can deal with it, I can decide myself what I want to
use.
I never worked
On Jun 7, 11:13 am, TreKing treking...@gmail.com wrote:
Q: Why is Android so buggy?
A: Because it's software - simple as that.
My software isn't that buggy. Neither is the iphone.
You compared Android to every existing piece of software there is?
No, but in my 16 years of commercial software
On Mon, Jun 7, 2010 at 7:50 PM, blahblah...@gmail.com
blahblah...@gmail.com wrote:
On Jun 7, 11:13 am, TreKing treking...@gmail.com wrote:
Q: Why is Android so buggy?
A: Because it's software - simple as that.
My software isn't that buggy. Neither is the iphone.
You compared Android to
On Mon, Jun 7, 2010 at 12:50 PM, blahblah...@gmail.com
blahblah...@gmail.com wrote:
My software isn't that buggy. Neither is the iphone.
No developer thinks their own software is that buggy - users usually
disagree =P
And the iPhone has the luxury of having been out for some time now and
Re: iPhone - Apple also has the luxury of controlling both the hardware
and the software.
Don't know how much is involved in porting Android to various phones,
but given that they don't have the same identical hardware, it's got to
be a pretty involved process.
Add to that phone
It seems that Android is very buggy
I think the reason is the one thing that no one ever talks about :
When we think google we think HUGE company. So we think of the Android
Team as A TEAM, like 50 or 150 persons maybe...
But I really get the feeling that Google isn't quite putting so much
On Mon, Jun 7, 2010 at 2:24 PM, Yahel kaye...@gmail.com wrote:
When we think google we think HUGE company. So we think of the Android
Team as A TEAM, like 50 or 150 persons maybe...
I am proud to be on the C team.
I would guess that at most there is 10 to 15 maybe less Google
employees in
Yeah, I also get the feeling that Google simply doesn't put enough
resources into Android. It's unrealistic to expect the open source
community to fix all the bugs. Chrome seems to be having similar
issues. It's a shame because I really like the idea of Android and it
could be amazing if they put
Dianne,
On 06/07/2010 11:51 PM, Dianne Hackborn wrote:
Our developer tools team is admittedly fairly small, and has done an
amazing job with the people they have. Also most of the stuff related
to these issues are in the open-source tree, so if they are trivial
issues someone could probably
On Mon, Jun 7, 2010 at 3:21 PM, Olivier Guilyardi l...@samalyse.com wrote:
For instance, how could someone feel like working on patch if the Git head is
hidden?
Since most of the bugs mentioned in the original email are developer
tools, I'll just say this: development for the SDK tools is done
On 06/08/2010 12:36 AM, Xavier Ducrohet wrote:
On Mon, Jun 7, 2010 at 3:21 PM, Olivier Guilyardi l...@samalyse.com wrote:
For instance, how could someone feel like working on patch if the Git head is
hidden?
Since most of the bugs mentioned in the original email are developer
tools, I'll
On 06/08/2010 12:46 AM, Olivier Guilyardi wrote:
On 06/08/2010 12:36 AM, Xavier Ducrohet wrote:
On Mon, Jun 7, 2010 at 3:21 PM, Olivier Guilyardi l...@samalyse.com wrote:
For instance, how could someone feel like working on patch if the Git head
is
hidden?
Since most of the bugs mentioned
At the risk of thread hijacking I'd like to personally thank Diane and
Romain for their posts, blogs, and articles without which my
development efforts would have been that much harder. I'd have to add
Mark Murphy into that too. So from one random developer, for what its
worth, thanks for your
On Mon, Jun 7, 2010 at 3:21 PM, Olivier Guilyardi l...@samalyse.com wrote:
This openness is your strength, and I think that it will lead to success if
you
manage to build an active community of contributors. I'm not monitoring
this
closely, but it looks like it is not the case (yet).
I think we all appreciate the work that Google has done in open-
sourcing Android. Like Olivier says, most of us don't have the time to
spend in fixing open source bugs.
Most of the bugs mentioned admittedly are easily worked around. The
only serious ones are the socket ioexception bugs, but
On Mon, Jun 7, 2010 at 4:04 PM, Dianne Hackborn hack...@android.com wrote:
Dalvik [is] now done in the open.
Actually, we're not developing in the open yet, but we are working
toward it. It is nontrivial to get there for all the reasons you cite.
-dan
--
You received this message because you
On 06/08/2010 01:04 AM, Dianne Hackborn wrote:
On Mon, Jun 7, 2010 at 3:21 PM, Olivier Guilyardi l...@samalyse.com
mailto:l...@samalyse.com wrote:
This openness is your strength, and I think that it will lead to
success if you
manage to build an active community of contributors.
On Mon, Jun 7, 2010 at 4:33 PM, Olivier Guilyardi l...@samalyse.com wrote:
I think that your problem is that the whole of Android is too monolithic. You
are mentioning branches where you could think in terms of standalone modules.
monolithic? Have you looked at git.source.android.com ? There
On 06/08/2010 01:48 AM, Xavier Ducrohet wrote:
On Mon, Jun 7, 2010 at 4:33 PM, Olivier Guilyardi l...@samalyse.com wrote:
I think that your problem is that the whole of Android is too monolithic. You
are mentioning branches where you could think in terms of standalone modules.
monolithic?
Like Olivier says, most of us don't have the time to
spend in fixing open source bugs.
What do you think the free phones are for.
Did you really think they were free.
Steve
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this
28 matches
Mail list logo
