Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google's playing the closed-open game again, this time with HTML5

extremetech.com

Post reply on HN
Print view View original

21–30 of 65 posts

Re: Google's playing the closed-open game again, this time with HTML5

#21

Post by tsuraan »

angryasian wrote: post #13
mrpollo wrote: post #10

It is clear to me that this is a Google Chrome Experiment, from their labs, and that they did not had any intention of it working on any other browser but i got curious... i was doing some research on it and they appear to be using sync xhr calls which causes FF to hiccup even after all this time. https://bugzilla.mozilla.org/show_bug.cgi?id=383304 https://bugzilla.mozilla.org/show_bug.cgi?id=313646 they are marked a…

this article is written with the obvious intention of bashing google, the writer didn't even do his research because honeycomb 3.2 source is available.

Where? http://source.android.com/ just says 2.3 is available, and google isn't turning up anything either.

EDIT: looks like the GPL/LGPL parts have been released (according to news reports, anyhow). Can you point me to a full buildable android 3.2 repo?

Re: Google's playing the closed-open game again, this time with HTML5

#22

Post by jannes »

jrockway wrote: post #14

All I get out of this is that Google calls their web browser "Chrome", while Apple calls theirs "HTML5".

I don't get why this is downvoted. You are right. At least Google explicitly marked this as a "Chrome experiment" instead of labeling it as a "HTML5 showcase".

Re: Google's playing the closed-open game again, this time with HTML5

#23

Post by jarin »

tomlin wrote: post #8

This is precisely the same kind of trickery Apple pulled with its HTML5 Showcase for Safari, which locked out other more compliant browsers in order to make Safari shine line a beacon of hope for open web standards. But Google isn’t building these experiences to make the web look good: it’s building them to make Chrome look good. I don't get this bit. Isn't Google doing the same as Apple, then?

Remove the word "But" and it makes logical sense.

Re: Google's playing the closed-open game again, this time with HTML5

#24

Post by icebraining »

ZoFreX wrote: post #17

Disappointing article, given all the other ways in which Chrome is harming the web. Example: There's a bug on a site I made in Chrome. It is categorically incorrect behaviour on the part of Chrome, it breaks the specs in order to be faster. How do I fix the bug? By calling a proprietary interface in Javascript that only exists in Chrome. Yup, that's right - to make my standards-compliant web page work, I have to do b…

Have they acknowledged the bug and refused to fix it?

Re: Google's playing the closed-open game again, this time with HTML5

#25

Post by darshan »

tsuraan wrote: post #21
angryasian wrote: post #13

Earlier quoted context omitted.

this article is written with the obvious intention of bashing google, the writer didn't even do his research because honeycomb 3.2 source is available.

Where? http://source.android.com/ just says 2.3 is available, and google isn't turning up anything either. EDIT: looks like the GPL/LGPL parts have been released (according to news reports, anyhow). Can you point me to a full buildable android 3.2 repo?

Only the GPL/LGPL parts are available, but the Honeycomb code isn't viewed as ready for public consumption yet. My guess is that we'll finally see the code when Ice Cream Sandwich rolls out.

Re: Google's playing the closed-open game again, this time with HTML5

#26

Post by azakai »

szarecor wrote: post #12

meh -- this is not an assault on openness, it's a silly little music video. Locking other browsers out of gmail, gmaps, youtube, etc would be an assault on openness.

That would have been a much bigger assault on openness, to be sure. But this is quite bad as well - it clearly shows that Google cares more about pushing Chrome itself than pushing the open, standards-based web. As the article says, when Microsoft's web demos are more standards-based than Google's, you know something is messed up.

Not so long ago I don't think Google would have done such a thing. Apparently though there are changes happening.

Re: Google's playing the closed-open game again, this time with HTML5

#27

Post by heydenberk »

It's a shame that an exaggerated article about a browser-sniffing art project that Google worked on is bound to get more attention from the public than, say, the contemporaneously front-paged [open sourcing of LevelDB](http://google-opensource.blogspot.com/2011/07/leveldb-fast-p...), which is a far more significant step in the direction of openness.

Re: Google's playing the closed-open game again, this time with HTML5

#29

Post by mrpollo »

pornel wrote: post #20
mrpollo wrote: post #10

It is clear to me that this is a Google Chrome Experiment, from their labs, and that they did not had any intention of it working on any other browser but i got curious... i was doing some research on it and they appear to be using sync xhr calls which causes FF to hiccup even after all this time. https://bugzilla.mozilla.org/show_bug.cgi?id=383304 https://bugzilla.mozilla.org/show_bug.cgi?id=313646 they are marked a…

That would explain blocking of Firefox, but they're blocking Safari and WebKit nightly and... everything else that doesn't have "Chrome" in User-Agent string: http://yfrog.com/z/kh1rylsqj

i just tried accessing the app with Safari and it came to my attention that its trying to load mp4 and mp3 files instead of the webm videos http://yfrog.com/h7x8xup then i got even more curious and found this file http://www.allisnotlo.st/static/js/VideoList.js look around line 236

this.src = src.replace(/(\.webm+)$/, (navigator.userAgent.indexOf('Chrome/') == -1 && (navigator.userAgent.indexOf('MSIE') != -1 || navigator.userAgent.indexOf('Safari/') != -1)) ? '.mp4' : '.webm');

but looks like they didn't upload any mp4 files :( sad

Re: Google's playing the closed-open game again, this time with HTML5

#30

Post by jackolas »

darshan wrote: post #25
tsuraan wrote: post #21

Earlier quoted context omitted.

Where? http://source.android.com/ just says 2.3 is available, and google isn't turning up anything either. EDIT: looks like the GPL/LGPL parts have been released (according to news reports, anyhow). Can you point me to a full buildable android 3.2 repo?

Only the GPL/LGPL parts are available, but the Honeycomb code isn't viewed as ready for public consumption yet. My guess is that we'll finally see the code when Ice Cream Sandwich rolls out.

Some openness. Waiting for corporations to deem it fit for public scrutiny but not public usage? Makes me suspicious if they released all the GPL'd parts or if they missed some.
Post reply on HN