Live data from Hacker News

Chrome is Not the Standard

chriskrycho.com

211–220 of 465 posts

Re: Chrome is Not the Standard

#211
post #4

I know they screwed up recently with the Mr. Robot malware, but I think it's really important for developers to get behind Firefox again. As the American government fails to provide any sort of check on its behemoth corporations (Apple, Google, and Microsoft) and to protect consumer privacy, Firefox is basically the last contender for real consumer protection standing.

I’ve found a lot of people are quite naively idealistic around browser development. The rendering, JS engines in Firefox and Chrome are state-of-the-art and take small armies to build and maintain. Mozilla has to strike a balance between revenue seeking and consumer protection seeking behavior that I would imagine is quite difficult to maintain. Lots of people here additionally are up in arms their incredibly specifi…

> Lots of people here additionally are up in arms their incredibly specific workflow was upheaveled by a movement to webextensions planned like 2 years in advance.

Maybe their incredibly specific workflow involves a piece of multi-million dollar equipment and updating to a new API involves reflashing its firmware for some crazy reason. (alternately, 100 $200 pieces of equipment in hard-to-reach places that must be manually reflashed.)

2 years may be roughly the maximum attention span of a software project, but 5 years seems like a better number for bedrock systems like web browser.

I don't mean to trivialize what goes into Firefox, just that backwards compatibility is a big deal and most software companies don't take it seriously enough.

Re: Chrome is Not the Standard

#212
post #4

I know they screwed up recently with the Mr. Robot malware, but I think it's really important for developers to get behind Firefox again. As the American government fails to provide any sort of check on its behemoth corporations (Apple, Google, and Microsoft) and to protect consumer privacy, Firefox is basically the last contender for real consumer protection standing.

I’ve found a lot of people are quite naively idealistic around browser development. The rendering, JS engines in Firefox and Chrome are state-of-the-art and take small armies to build and maintain. Mozilla has to strike a balance between revenue seeking and consumer protection seeking behavior that I would imagine is quite difficult to maintain. Lots of people here additionally are up in arms their incredibly specifi…

> Lots of people here additionally are up in arms their incredibly specific workflow was upheaveled by a movement to webextensions planned like 2 years in advance.

They're up in arms because of an upheaval which prevents anyone from restoring their workflow: the new extensions API simply does not allow the extensibility the new extensions API allowed. Some of the changes are arbitrary (e.g. it's not possible to rebind C-n).

The move to Quantum is awesome, but the permanent loss of functionality is not.

Likewise, the security reversion in the Sync protocol is another unforced error.

Re: Chrome is Not the Standard

#213
post #198

Earlier quoted context omitted.

> 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.

Fair enough, but mind that asm.js is itself being deprecated too, WebAssembly is meant to replace it.

It was as cool experiment by Mozilla for sure, but it's in the same boat as the cool experiments by Chrome: not picked up by other browsers.

Re: Chrome is Not the Standard

#214

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

Given this it's really a shame that Apple does not allow other browser engines on iOS. Would be a prime opportunity for competition to raise the overall quality level.

Re: Chrome is Not the Standard

#215
I've always hated IE, and I've never been an MS fan, but I tried Edge and I was surprised how fast it was. I just use it to test website and app I work on, so I don't have a good idea on how good it is as a browser (bookmark, privacy, plugins...).

Re: Chrome is Not the Standard

#217

Earlier quoted context omitted.

The Mr. Robot thing was not "malware". It was an easter egg, just like about:mozilla. You may say it was poor taste on Mozilla's part, since it was essentially a paid-for promotional tie-in with a TV show, and I would probably agree with you. But it did not damage anyone's computer, compromise any data or do anything that could put it on the "Malware" category. Something similar that noone has complained about are th…

Note that the advertisement was for a TV show _owned by a company that helped destroy net neutrality_: Comcast. How am I supposed to "Join Mozilla in defending it" (from mozilla.org) when they are going to work for their own enemies?

That's an interesting aspect I did not consider. (I had no idea it was a TV show owned by comcast)

Re: Chrome is Not the Standard

#218

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

Based on this you either never had to work with IE6 compatibility, or you have a really bad memory.

Not least most of what you mention (other than the 300ms delay) is OS level anyhow.

Re: Chrome is Not the Standard

#219
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?

People who wanted to solve the Mr. Robot ARG/puzzle had to download Firefox to complete the part of it the add-on enabled.

Re: Chrome is Not the Standard

#220
post #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 a…

What reduction in bug rate should we expect for each, day, $100M invested?
Post reply on HN