4 ms·
1. Adobe is/was on the standards groups and stnadardised all the photoshop blend modes into browsers a long long time ago. 2. Alpha composition? Are you sure t
by ZenPsycho 7y ago
1. Adobe is/was on the standards groups and stnadardised all the photoshop blend modes into browsers a long long time ago.
2. Alpha composition? Are you sure that's what you mean? we've had that universally in browsers since IE7.
I am continually stunned at how little most developers know of what browsers are capable of.
- amelius 7y ago> I am continually stunned at how little most developers know of what browsers are capable of. I guess it's because developers don't always need to know everything. The browser platform has turned native computational capabilities into a "hodge podge" of functionalities that a developer needs to pick from, so programming becomes more like shopping than like building things. Not every developer likes that mindset.
- ZenPsycho 7y agoReally? the only place you wouldn't find that is in Assembly language on baremetal. Even C has platform libraries and system calls. I haven't seen a more dithered and inconsistent "hodge podge" than when trying to get something as simple as a timer working consistently across all the Unix-likes. Browsers are just a platform like any other, you work with the platform capabilities the OS or platform gives you. what alternative do you think there is?
- dahart 7y agoI’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]