All of the problems you list are also problems for application developers. I think knowing the feature set of interest reduces the matrix by only a small amount.On 2014/01/15 13:57, Brandon Jones wrote:
Maintaining a per-feature performance characteristics list like that would be incredibly difficult for several reasons:
- There are a lot of features to test, and the list grows with extensions.
- Features may work well in isolation, but interact badly with other features in unpredictable ways
- Features may only perform badly in certain use-cases, but fine otherwise.
- "Slow" is highly subjective.
- There is a steady stream of new hardware coming out that the browsers would need to continuously test an maintain detailed performance characteristics for.All of this makes it unreasonable for browsers to try and track this information, and makes the usefulness of it limited to developers. On the other hand, developers know the feature set they care about. By giving them a method to track performance vs. hardware we allow them to make intelligent decisions about when and how to react to known-bad configurations.
What does Google Maps do when it encounters a unknown GL_RENDERER string?
注意：この電子メールには、株式会社エイチアイの機密情報が含まれている場合が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情報の使用を固く禁じております。エラー、手違いでこのメールを受け取られましたら削除を行い配信者にご連絡をお願いいたし ます.
NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.