Live data from Hacker News

Everything You Need to Know About the CSS will-change Property

dev.opera.com

61–64 of 64 posts

Re: Everything You Need to Know About the CSS will-change Property

#61
This is a hack to patch a bug produced by optimization on the browser side.

I get that it's a neat hack. I really do. But this should never become standard. It just shouldn't.

I guess it beats having a videocard optimized for rendering webpages, which is probably the alternative.

Can we just clean slate reboot HTML/CSS/JavaScript to something that's quite like it but has reinvented seperation of concerns? Symantics/Syntax/Dynamics was kinda neat. Right now it's "State/Looks/Processing", and it's backwards compatible in a messy way.

I seriously think that HTML5 is just too cluttered, with no cleaning up going on. Compiling towards HTML5 is not improving the problem, and if we go down that road I suggest making languages better for compiling towards web-compatible(Hey, c, how are you? What's that? You're in browsers now?).

Re: Everything You Need to Know About the CSS will-change Property

#63
post #62

Mostly technical article about CSS opening with explanation of what CPU and GPU are and where they are located. I'm very surprised that those two terms even need explanation.

Acceleration using the GPU is what will-change is all about.

Also, especially among web developers there are many people who barely know what they are doing, so it's a good idea to comprehensively cover the context (I know it helped me, since I'm mostly a back-end developer who does some front-end on the side).

Post reply on HN