54 ms·

The "is houdini ready yet?" section is dishonest even though it's factually correct. And this shows that Chrome is the new IE. If you're not careful, you may c

The "is houdini ready yet?" section is dishonest even though it's factually correct. And this shows that Chrome is the new IE. If you're not careful, you may come away reading that "is houdini ready yet?" section thinking it's mostly supported by most browsers except for some laggards like Webkit and Firefox. Except that, if you exclude those two, the rest of the browsers displayed in the chart are basically Chrome forks. Normally in the past, something like this would have been packaged as some "Google experiment", but now their "blink engine" trojan horse has penetrated other browser vendors, they are using that to paint a misleading picture to push their agenda. Just to be clear, sure this technology is cool, but this is defacto "Google chrome experiment", not a web standard supported by various independent browsers. It's basically Chrome and other small fish browsers that depend on Chrome. Google should stop misleading the public about browser support of whatever they're releasing. It's dishonest. On the other hand, I really think time is ripe for the next disruption of web browsers.

franklampard 6y ago
The new IE is Edge, which isn’t a small Fish either
- cocktailpeanuts 6y ago
  What i meant by small fish is, they depend on Blink engine. They have to follow whatever Chrome does.
- extra88 6y ago
  When someone writes "X is the new IE," they don't mean it's the new browser from Microsoft, they mean one of two things: 1) "X" dominates browser market share to such a degree that many developers won't bother testing in any others, as IE once did. That could describe Chrome, especially if you include other Chromium-based browsers, like Edge. 2) "X" is lagging in support of web standards and holding back use of those standards by developers. That second claim doesn't fit Chrome well, it's more typically used against mobile Safari. The combination of mobile Safari's share of mobile traffic, relatively slow feature release pace particularly for features in certain segments (PWA), its exclusivity on Apple mobile devices, and the longevity of said devices makes the claim somewhat accurate though still far from the miserable standard set by IE.
  - joshspankit 6y ago
    Don’t forget 3) That dominance is used to break standards and push “new features” that only work in X, forcing web designers to buy in or lose viewers
  - franklampard 6y ago
    I find it hard to compare Chrome to IE. Except for their similarity in its market share dominance, they are nothing alike really. Chromium is open-source, developer friendly and progressive. The Old IE is just not the same
bsimpson 6y ago
At least for paint, there are equivalents in other browsers. -webkit-canvas serves the same purpose in Safari as paint worklets do in Chromium. Standardizing these APIs is a good thing, because it empowers people to make use of them. Looks like there's a polyfill that lets you use the same paint worklet across the major engines: https://github.com/GoogleChromeLabs/css-paint-polyfill https://github.com/GoogleChromeLabs/css-paint-polyfill
jahewson 6y ago
I dunno. The Houdini concept has been around for a few years now and has been positively received. The W3C draft has contributions from Google, Apple and Microsoft.

franklampard 6y ago

The new IE is Edge, which isn’t a small Fish either

cocktailpeanuts 6y ago
What i meant by small fish is, they depend on Blink engine. They have to follow whatever Chrome does.
extra88 6y ago
When someone writes "X is the new IE," they don't mean it's the new browser from Microsoft, they mean one of two things: 1) "X" dominates browser market share to such a degree that many developers won't bother testing in any others, as IE once did. That could describe Chrome, especially if you include other Chromium-based browsers, like Edge. 2) "X" is lagging in support of web standards and holding back use of those standards by developers. That second claim doesn't fit Chrome well, it's more typically used against mobile Safari. The combination of mobile Safari's share of mobile traffic, relatively slow feature release pace particularly for features in certain segments (PWA), its exclusivity on Apple mobile devices, and the longevity of said devices makes the claim somewhat accurate though still far from the miserable standard set by IE.
- joshspankit 6y ago
  Don’t forget 3) That dominance is used to break standards and push “new features” that only work in X, forcing web designers to buy in or lose viewers
- franklampard 6y ago
  I find it hard to compare Chrome to IE. Except for their similarity in its market share dominance, they are nothing alike really. Chromium is open-source, developer friendly and progressive. The Old IE is just not the same

bsimpson 6y ago

At least for paint, there are equivalents in other browsers. -webkit-canvas serves the same purpose in Safari as paint worklets do in Chromium. Standardizing these APIs is a good thing, because it empowers people to make use of them. Looks like there's a polyfill that lets you use the same paint worklet across the major engines: https://github.com/GoogleChromeLabs/css-paint-polyfill https://github.com/GoogleChromeLabs/css-paint-polyfill

jahewson 6y ago

I dunno. The Houdini concept has been around for a few years now and has been positively received. The W3C draft has contributions from Google, Apple and Microsoft.