Hacker Newsnew | past | comments | ask | show | jobs | submit | zeddez's commentslogin

Google pays $140 Million a year to Firefox to be the search default. Given the choice, I believe they would prefer to keep the $140 Million and just have people use Chrome.


Yes. Use an Android device with Chrome. Most users are stuck with whatever came from the phone. iPhone far outperforms in terms of % upgrades.

http://developer.android.com/resources/dashboard/platform-ve...


Chrome does not run on Android.


There is a difference between direct and indirect patent infringement. Google provides the Android source, but the companies that are being sued are directly infringing by selling and distributing products based on these patents. http://en.wikipedia.org/wiki/Patent_infringement_under_Unite...

Google naturally has the choice to indemnify Android distributors and protect them from patent infringement. Google chooses not to do this, presumably because they do not want to expose themselves to the costs of direct patent infringement.


Does the Nexus One or Nexus S blur this line at all? In that case, it seems like Google is doing more than simply making the source code available. Those phones actually carry its brand.


Microsoft has a deal with Samsung already in place. See: http://news.cnet.com/Microsoft%2C-Samsung-in-patent-swap-dea...

the software maker specifically notes that the deal will allow Samsung to offer products using Linux without concern that Microsoft will sue it or its customers.

And another deal with HTC. http://www.androidguys.com/2010/04/28/htc-pay-microsoft-roya...

So both of those phones are covered.


According to the official breakdown of Android devices by OS version only 0.6% of devices are on 3.0 or later. http://developer.android.com/resources/dashboard/platform-ve...

And even devices with the same version of Android will have differences.


Sorry, what is the point of your response?


Social is too important for one company to control the market. This is a great start for Google+, but Google is fighting with one arm behind their back given the network effects of Facebook.


You mean pimply and with a bad attitude :)


Some of the most interesting work is only hinted at in the blog. IE 10 PP2 now leads on EcmaScript standards conformance.

IE 10 only fails 7 tests compared to 200 for Firefox 5 out of a total of 10000 tests.

I don't use Opera, but according to this page http://en.wikipedia.org/wiki/ECMAScript Opera lags the other browser and fails 3000 tests. Does anyone have Opera and willing to run the conformance test here: http://test262.ecmascript.org/


Opera version 11.50 (most recent) on Win7:

Tests To Run: 10935 | Total Tests Ran: 10935 | Pass: 7061 | Fail: 3874 | Failed To Load: 66

The fast majority (80%) of the error log appears to be in section 15.2.3, with half of the rest also being in section 15. This would imply that around 1/3 of the entire test suite is just in that section of the specification; as the test itself describes, its coverage is currently incomplete.


I was pretty certain that Opera's reported score couldn't be that bad. I am definitely very suprised.

Overall, I have to say, I am a huge fan of having these thorough tests come to web standards. So that browsers can't just say "We support HTML5". I am really tired of the buzzword nature of standards recently. Hopefully, this will get all browsers to step up their game.


FF5 is a production release, IE10 is a "platform preview". Not exactly a fair comparison.


That's a good point. It would be interesting to get a read on the latest Aurora builds. I might install it and do it later today.


I can help with that, I am running Nightly 7.0a1 (2011-06-29) My results: Tests To Run: 10935 | Total Tests Ran: 10935 | Pass: 10732 | Fail: 203 | Failed To Load: 0


Then FF5 should fail less of the tests, right? Since a production release should be more stable than a platform preview?


i get the same type of result for 'gmail'. Most of the queries result in pictures of women showing panties or in thongs.


The core issue is this - enterprises can reduce testing and maintenance costs for their internal apps because they can control and standardize their browser enviroment. Sites that cater to users at large (like a yahoo) have no control over what browsers their users choose. So, they have to bear significantly higher testing costs.

I haven't heard a persuasive argument for enterprises to change their web development practice and bear significantly higher testing costs. So my expectation is that they will continue on the path that they have been on traditionally.


This was not the best way to ease users into the new Firefox versioning and the associated benefits.

If there had been something subtantial in 5, it might have worked. But it seemed more like an update for the sake of versioning.

They could probably have gotten away with this later, but first turn of the crank just opens them up for complaints.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: