Live data from Hacker News

Chrome is Not the Standard

chriskrycho.com

201–210 of 465 posts

Re: Chrome is Not the Standard

#201
Firefox's webGL support is abhorrent. Microsoft is undoing some aspects of their browser/OS decoupling. Google is no longer Don't Be Evil. Honestly without that getting better, I think the browser wars are pretty much moot.

Re: Chrome is Not the Standard

#202
post #198

Earlier quoted context omitted.

> IE literally refused to implement standards Chrome doesn’t implement asm.js (EDIT: I had previously written WebAssembly, but that was a typo), concurrent JS, or autocomplete=off, or the GeoLocation API via HTTP, etc. > allowed for proprietary native extensions and had many different apis NaCl, PNaCl. Try running http://earth.google.com/ in a browser other than Chrome. Or the Google Hangouts Video Chat. > They had 9…

> Chrome doesn’t implement WebAssembly > NaCl, PNaCl. It does, and both of which are being deprecated and removed in favor of WebAssembly. At least your point about Google using underhanded tricks to get Chrome in the hands of users is accurate.

Thanks, I meant asm.js instead.

Re: Chrome is Not the Standard

#203
post #61

Earlier quoted context omitted.

>>Mozilla's biggest screw up IMO was failing to disclose properly what was going on. That was not the only issue 1. Failure to Disclose it before distribution 2. Failure to Properly name or provide any support context to the Add In. 3. Using the "Studies" System designed to improve the technology and advance the web browser for this Adware "Easter egg" not really an Easter egg addin 4. Failure to Publicly Comment abo…

Then you can go back to chrome or chromium, both of which Google has pushed a binary plugin to that records voice in the past. Debian had to raise a storm over it and turned into a compile-time only option to not get the microphone listening plugin on your chromium install.

Fine, but that doesn't make the points in the comment you're replying to any less valid. That's... not how it works.

Re: Chrome is Not the Standard

#204

Earlier quoted context omitted.

Yes thank you, I understand all of that - it's very well known among web developers. None of it changes my argument: The majority of the functionality that we care about in our web browsers comes from an open source library.

Except it does change your argument: you are clearly missing a for now , so long as it pleases Google. You can imply that if Google did something to upset consumers they may flock to an alternative Blink-based browser or Chromium, but Google and Chrome are the brands they know, they don't know or care about Blink or Chromium. You may believe that Google are entirely generous and would never upset the open source bala…

Incorrect. We have the source, we can do whatever we want with it. Nothing that you said changes that.

Re: Chrome is Not the Standard

#205
post #95
post #51

Earlier quoted context omitted.

> it was essentially a paid-for promotional tie-in From what I recall, it wasn't paid-for either. > we developed an unpaid collaboration to engage our users and viewers of the show in a new way Source: https://blog.mozilla.org/firefox/update-looking-glass-add/

If they didn't get paid, why on earth did they do it?

bribery

Re: Chrome is Not the Standard

#206

Earlier quoted context omitted.

I think there may even be a chicken and egg situation going on - for some reason, media websites such as CNN are pushing giant rich media content objects at us like videos, which obviously are meaningless to a text browser. Even webdev blogs are being posted with big GIFs every paragraph or two. I'm not sure why content creators are feeling the need to go multi-media - perhaps it's getting harder and harder to tell w…

Back when going multimedia was very primitive and was clearly just a shiny feature with no direct benefit to anyone other than for the creators to partake in new world, I'd have agreed with your statement. In the current situation of muted Facebook videos being a major form of (dis)information distribution, everyone can point to all-encompassing multimedia communication as a potentially extremely lucrative medium. Th…

This leads to some perverse incentives, though...I have started to see like-farming "tag your friends" pages will post a video of a static image, overlaid with a subtle movement effect like falling snow, undoubtedly because someone realized they'll get more eyeballs from the all-knowing News Feed algorithm if their content is video.

Re: Chrome is Not the Standard

#207
I wish the author discussed the fact that Apple doesn't allow any other browsers to target the iOS platform. Chrome / Firefox are forced to be thin wrappers against the webkit engine instead of bringing their own technology.

No other platform has policies like this and it greatly impacts the web platform and changes the dynamic of web standards in a way no other browser developer could.

Re: Chrome is Not the Standard

#208

"Safari ships new features on a much slower cadence, but they’re usually solid and always perform incredibly well" Well, clearly this person doesn't have much experience with web development... The webengine in iOS is the biggest pile of crap I've ever worked with since IE6. "Oh? You want to click this? OK, let's wait for 300 ms just in case you want to double tap to scroll!" "We finally fixed it, no more delay on cl…

What really sucks is that Apple has TENS OF BILLIONS of dollars in cash, and yet can't be bothered to throw a billion at fixing iOS, iOS safari and MacOS bugs.

Its quality really went downhill. I really loved the "it just works" stuff of Apple Past. And I loved the intuitive, skeumorphic interfaces.

Now it's all crap and HIDDEN MODES - something Apple always spoke against in its UX manuals. It's sad day that Google and Microsoft have better design than Apple now, and Apple copied them.

Steve Jobs would have never let this happen. He would have a whole department funded with several billion dollars just to make Apple products the most user friendly on the planet. And he would have Siri be a Star-Trek-like voice platform by now.

Re: Chrome is Not the Standard

#209
post #104

Earlier quoted context omitted.

> Google is transparent. I know what they are doing. You do? Okay, I don't. Please, show me exactly how Google uses data they collect from their users. Every usage. Not just a few. And no "but they say they can use it for whatever they want!" - then we can talk about transparency.

Sure it is - it markets my information to advertisers via its own platform. It is my neighborhood drug dealer, and drug are pretty good - nicely packaged and no one fucks with me when i use its drug delivery service. Mozilla is pretending to be a health store. But we are starting to see that they are also peddling drugs. Not Google drugs - drugs with security and drugs with delivery system and drugs that we are prett…

> it markets my information to advertisers

and what other uses?

Re: Chrome is Not the Standard

#210

"Safari ships new features on a much slower cadence, but they’re usually solid and always perform incredibly well" Well, clearly this person doesn't have much experience with web development... The webengine in iOS is the biggest pile of crap I've ever worked with since IE6. "Oh? You want to click this? OK, let's wait for 300 ms just in case you want to double tap to scroll!" "We finally fixed it, no more delay on cl…

I discovered that having an onScroll event handler on a div with overflow and -webkit-overflow-scrolling: touch resulted into weird visual artifacts under certain conditions. And no, I don't want to override native scroll (which is often a bad idea), I want to react to the scroll.
Post reply on HN