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

31–40 of 65 posts

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

#31

Post by mrpollo »

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.

"this article is written with the obvious intention of bashing google" i agree, it is way faster to develop for just 1 browser, plus we should be celebrating people are trying to break ground doing this awesome videos, i can only begin to imagine all the impressive work that what went into this video, good one google +1

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

#32

Post by jmesserly »

icebraining wrote: post #24
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?

Agreed, it would be nice to see the bug. AFAIK they take standards compliance pretty seriously. I'm sure someone would look at it, especially if Chrome is behaving differently from FF/IE9/Safari.

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

#33

Post by CrazedGeek »

mvzink wrote: post #9

Useless article. This has nothing to do with "openness", just marketing: what is Google's incentive to building the site in the first place if they can't make people download Chrome to view it? That said, they could at least add a "Try it anyway" button for other browsers.

They had a "Try it anyway" link for "3 Shades of Black": http://ro.me

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

#34

Post by pornel »

mrpollo wrote: post #29
pornel wrote: post #20

Earlier quoted context omitted.

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 || navig…

None of this '90s-style sniffing is necessary: HTML5 supports multiple elements allowing browser to choose and has canPlayType('video/webm') for JavaScript.

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

#35

Post by drcube »

mvzink wrote: post #9

Useless article. This has nothing to do with "openness", just marketing: what is Google's incentive to building the site in the first place if they can't make people download Chrome to view it? That said, they could at least add a "Try it anyway" button for other browsers.

Chrome is free. Google builds websites to attract advertisers. Which makes Google's lack of openness all the more perplexing.

And what's this about not being able to get the Android source!? I'll buy an iphone right now if that's true. At least Apple doesn't try and pretend they're not evil.

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

#36

Post by starwed »

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.

Sure, but that was exactly what the author meant.

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

#37

Post by Sukotto »

jannes wrote: post #22
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".

How are you seeing the vote count? I don't see a way in my profile to turn it back on

[Edit to add] It's a serious question. Parent refers to downvotes of GP post. That makes me wonder if there's a way to turn the numbers back on. Something I would very much like to do.

Why the downvotes?

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

#38

Post by ZoFreX »

icebraining wrote: post #24
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?

One of them is already getting attention so hopefully they will notice (you know how it is), the other one has literally only affected me as far as I can see and I haven't put together a minimal test case yet. It's a weird one!

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

#39

Post by bonch »

mrpollo wrote: post #31
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.

"this article is written with the obvious intention of bashing google" i agree, it is way faster to develop for just 1 browser, plus we should be celebrating people are trying to break ground doing this awesome videos, i can only begin to imagine all the impressive work that what went into this video, good one google +1

I thought the point of open standards was that you didn't develop for just one browser. Google loves to trumpet its openness a lot, so forgive me for being confused by their motives.

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

#40

Post by bonch »

heydenberk wrote: post #27

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.

"Exaggerated article about a browser-sniffing art project"? It's bizarre how Google defenders justify things that Apple was bashed for when it put Safari-exclusive HTML5 demos up on its website. I guess Google's ploy works on you--if they talk about "openness" a lot, they get a free pass.
Post reply on HN