4 ms·
I’d guess the vast majority of web developers never use WebGL or Canvas directly. The alpha compositing we are talking about here is one of those, not the nativ
by dahart 7y ago
I’d guess the vast majority of web developers never use WebGL or Canvas directly. The alpha compositing we are talking about here is one of those, not the native compositing, because you wouldn’t use native compositing for image editing.
- ZenPsycho 7y agoI would be very surprised if there were ever a version of CANVAS or WEBGL that didn't have alpha compositing. Sounds like the product of an extremely disparaging imagination.
- dahart 7y agoWhat’s with all the negativity? I didn’t remotely suggest that WebGL or canvas ever lacked compositing, so I’m pretty confused by your response and where the attempted insult came from, or why. Maybe you’ve misunderstood. Browsers can composite elements without using WebGL or canvas, so sure most devs should know that. And, turns out they do. But most devs never need to interact directly with canvas or WebGL, so why would they know about the specific compositing modes? Most of the small number of people who do use WebGL or Canvas have never used any of the other Porter-Duff compositing modes other than “over”, and most of them have never used premultiplied alpha. It seems like no surprise at all that most people don’t know the minutiae and trivialities of what browsers can do using APIs that the majority of devs don’t use. To flip that around, there are plenty of WebGL devs who know compositing modes and yet barely know anything about browser networking, security, and caching features.
- deleted 7y ago[deleted]