If and when it does, I hope people just use SVG instead of redesigning SVG as OpenType features one feature at a time.
-
-
Replying to @rocallahan @Gankra_
And FWIW there is no need to be discreet by repeatedly referring to "someone" :-)
1 reply 0 retweets 3 likes -
-
Replying to @rocallahan
I mean, for partial-ligatures I linked your post on it, so I wasn't obscuring anything. The others I genuinely wasn't sure it was you (although they all have the a distinct "roc went on an adventure" signature).
1 reply 0 retweets 6 likes -
Replying to @Gankra_ @rocallahan
Everything I discussed except the the partial ligature work turned out to be a bad gamble, but they were reasonable considerations at the time. They stand out to me because they were bizarre friction points I ran into when bringing up webrender which no other browser did.
1 reply 0 retweets 2 likes -
Replying to @Gankra_
I don't see a clear case that component alpha was a "bad gamble". Its useful life probably ended a while ago but that doesn't necessarily mean it was net detrimental.
1 reply 0 retweets 2 likes -
Replying to @rocallahan
As we've pushed into high resolutions driven by relatively weak gpus, and pages have started producing more nasty layers, the extra memory/bandwidth footprint from component alpha appears to actually be causing problems. Also no one else ever bothered doing it, right?
2 replies 0 retweets 2 likes -
Replying to @Gankra_ @rocallahan
Is the extra memory/bandwidth from component alpha theoretically necessary or is it just a consequence of GL 3 blend modes being overly limited? (I forget how component alpha works)
1 reply 0 retweets 0 likes -
It’s worth remembering that we in the browser space are in a weird situation where we can’t rely on anything past D3D9 level functionality which is from 2002 (!!) When I talk to game developers about this they’re often aghast.
1 reply 1 retweet 8 likes -
Component alpha needs 6 bytes per pixel rather than 4. That's fundamental extra overhead. I don't remember how it's implemented in the GPU compositors.
2 replies 0 retweets 1 like
Ah, OK. Yeah, that will halve your fill rate. (Unless you can do something clever like rendering to an RGB16U frame buffer and pack bits manually and somehow get the blending right…probably not feasible.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.