5 ms·

> If it works as intended on Chrome, it’s ready to ship A great step Firefox could take in this space is improving the transparency and performance auditing of

> If it works as intended on Chrome, it’s ready to ship A great step Firefox could take in this space is improving the transparency and performance auditing of its own engine. Debugging rendering performance issues between browsers is still an absolute nightmare. If Firefox can provide a better developer experience than Chrome, it might increase the likelihood that web developers would use FF as their first-choice development platform for simplicity and utility of tools. If it doesn't, it may still decrease the odds that when faced with a nasty performance bug, developers will throw up their hands and say "Chrome does it right; I guess FF still just sucks for performance in this corner case." FF has been making impressive strides in this space, but their toolchain still feels clunky and slow relative to Chrome Developer Tools.

guitarbill 8y ago
I'm pretty sure this is a commentary on the laziness of devs/why browser dominance is bad for standards, when taken in context: > The dominance of Chrome has a major detrimental effect on the Web as an open platform: developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship. When you're following decently established standards (not bleeding edge), it's usually Chrome that breaks now, not Firefox or Safari. Chrome truly is the new IE.
- fixermark 8y ago
  I haven't personally encountered this phenomenon. Can you give an example of an established standard that breaks on Chrome but FF / Safari handle?
  - guitarbill 8y ago
    Indeed I can, although one anecdote does not data make. The latest was using SVG sprites as background in CSS I think. Maybe I can throw up a demo during my lunch break, but honestly it isn't that exciting. It just doesn't work correctly in Chrome, the sprite is cropped/has a weird rendering artifact.

guitarbill 8y ago

I'm pretty sure this is a commentary on the laziness of devs/why browser dominance is bad for standards, when taken in context: > The dominance of Chrome has a major detrimental effect on the Web as an open platform: developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship. When you're following decently established standards (not bleeding edge), it's usually Chrome that breaks now, not Firefox or Safari. Chrome truly is the new IE.

fixermark 8y ago
I haven't personally encountered this phenomenon. Can you give an example of an established standard that breaks on Chrome but FF / Safari handle?
- guitarbill 8y ago
  Indeed I can, although one anecdote does not data make. The latest was using SVG sprites as background in CSS I think. Maybe I can throw up a demo during my lunch break, but honestly it isn't that exciting. It just doesn't work correctly in Chrome, the sprite is cropped/has a weird rendering artifact.