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

Chrome is Not the Standard

chriskrycho.com

Post reply on HN
Print view View original

231–240 of 465 posts

Re: Chrome is Not the Standard

#231

Post by VikingCoder »

brians wrote: post #220
EGreg wrote: post #208

Earlier quoted context omitted.

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?

I can't tell you how many more meters per second you will get if you push harder on the gas... But I can tell you that pushing harder on the gas is likely to get you where you're going quicker.

Do we really need to discuss exact m/s before you're willing to push harder on the frickin gas?

Re: Chrome is Not the Standard

#232

Post by headmelted »

This isn't new, though.

I think people forgive Google for more because they like them. IE did exactly the same thing before Chrome and was roundly (and rightly) admonished for it.

In fairness, Chrome's proposals do seem to be designed with the open web in mind - at least insofar as being items that other projects could reasonably be expected to implement in their engines if they chose to do so.

There's nothing so egregious as IE's DirectX-filters-embedded-in-CSS nonsense - or shudder ActiveX - but it's still not great for the open web as a whole.

Re: Chrome is Not the Standard

#234

Post by threeseed »

user5994461 wrote: post #222
tpush wrote: post #214

Earlier quoted context omitted.

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.

Looks like a case for anti trust, just like microsoft had with IE.

1) iOS is not a monopoly.

2) Apple has legitimate technical reasons for not allowing other browser engines (well specifically the JS part). Intent matters.

Re: Chrome is Not the Standard

#235

Post by TazeTSchnitzel »

drvortex wrote: post #192

Standards are irrelevant to pragmatism. De facto standards are what is important. By virture of sheer popularity, Chrome is the de facto standard. And if they have provided anything that becomes useful or popular, then by virtue of popularity of that feature in what is already the post popular browser, makes that feature part of the de facto standard. The post is just pedantic whining about how something isn't accord…

Chrome isn't the de facto standard, it doesn't have complete dominance of the web yet so you also have to support, at the very least, Safari.

Re: Chrome is Not the Standard

#236

Post by scaryclam »

fixermark wrote: post #163
adregan wrote: post #100

Earlier quoted context omitted.

I switched to FF Developer Edition a little over a year ago, and I have caught several bugs that went unnoticed by my Chrome using colleagues.

How were they unnoticed in Chrome?

Chrome seems to have a tenancy to paper over some bugs and not report them back to the user (even in the console). It's the main reason none of our devs use Chrome for primary development anymore (it's not worth the extra dev time when QA fails on all other browsers) and it's just used during QA.

Re: Chrome is Not the Standard

#237

Post by mintplant »

foobarz wrote: post #190
c3534l wrote: post #119

Earlier quoted context omitted.

> revenue seeking Then what the hell did I donate money to them for? I thought their whole thing was they were for "people, not profit." I don't want my technology to make money off of me in any way I'm not aware of.

Besides, it looks like the amount of cash that Mozilla got for stuff like Pocket or Mr Robot is tiny compared to their other sources of revenue. It doesn't seem something worth to taint their brandname and ethos for. If you rule out Firefox, there's hardly any viable option for a modern, feature-complete and freedom-respecting browser. Chromium is OK, but those suspicious blobs don't look very appealing. For me the m…

For the record, Mozilla didn't get any money for the Mr. Robot tie-in: it was supposed to be part of a mutual cross-promotion campaign. I don't think the original Pocket integration was paid, either, though my memory there is hazy. Either way Mozilla now owns Pocket anyway.

Re: Chrome is Not the Standard

#238

Post by throwaway284534 »

NightlyDev wrote: post #169

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

Here here. The author clearly hasn't worked with Apple's implementation of Audio Context either. Granted the bar is pretty low compared to Chrome, but wow! What a mess. Safari consistently has latency and bit rate issues when playing even the smallest files.

Re: Chrome is Not the Standard

#239

Post by rdiddly »

4684499 wrote: post #174

There was a competition, Chrome won, I don't like the result, but it's the fact. I won't tell people to save the web by suggesting using something less competitive, that would reduce the I-wanna-save-the-web group's productivity, making their choices/opinions less competitive, which probably leads them to extinction. Web devs are just a small amount of browser users, general users couldn't care less about the standar…

Like it's over? You forget that one of the things that happens a lot before losing, is winning. Internet Explorer won too.

Re: Chrome is Not the Standard

#240

Post by chriskrycho »

drvortex wrote: post #192

Standards are irrelevant to pragmatism. De facto standards are what is important. By virture of sheer popularity, Chrome is the de facto standard. And if they have provided anything that becomes useful or popular, then by virtue of popularity of that feature in what is already the post popular browser, makes that feature part of the de facto standard. The post is just pedantic whining about how something isn't accord…

Not only did I not whine about something in a written document, I never once mentioned WHATWG or anything other standards body. (That was intentional.) I explicitly call out the vendors and their mutual implementations. The "standard" I care about is the truly living standard of what every browser implements. The point here is that the _de facto_ standard is not Chrome, and if it were that'd be a bad thing. (We've been there before; it was a bad thing.)
Post reply on HN