3 ms·
the whole screen is a big giant canvas. I don't necessarily think it was a diberate decision, but Fluttercs CanvasKit is one of the most pernicious evil backwa
by rektide 6y ago
the whole screen is a big giant canvas.
I don't necessarily think it was a diberate decision, but Fluttercs CanvasKit is one of the most pernicious evil backwards awful things anyone has done to the web and it absolutely will make ads much much much harder to block.
It uses the web like a vnc session to the app. It is an absolutely sickening perversion of the web & oh it so happens such ads will be unblockable, there'll be no imgs nor divs nor anything else to block, just one massive canvas pushing pixels at you. Gobsmackingly horrible regression for the web, & I am so so so glad someone did a proper job writing up this horrorshow.
- detaro 6y agoOh, fully agreed that it's a terrible idea on many levels that should be reserved for very niche scenarios(I don't think it's totally useless, and would be curious how well it can be expanded to add accessibility features if the developer cooperates). I just think negligence/ignorance/bad priorities are more likely explanations. (another technical argument: today you seldom see ads being served from the app domain, despite it being not that difficult and an easy way around domain blocks, because the ad industry doesn't trust that model - so even if the rendering is obfuscated, at least for now ads from Google would still be fetched through stoppable network requests for anti-fraud reasons)
- darepublic 6y agoI've heard it suggested that you can build an application fully in canvas but also leave behind a semantic and accessible skeleton for screen readers and crawlers
- rektide 6y agoThe two are not two different worlds. Screen-readers might be able to function off a semantic skeleton. But, as the author mentions, tools like Vimium are just going to be forever screwed over, totally shot the hell out of the water, by this post-hypertext abomination. CanvasKit!!!!!!!!!!