Re:Houdini: Maybe the Most Exciting Development in CSS
by mrec on Thursday March 24, 2016 @10:23PM
(#11358104)
I didn't get the impression from that article that "replace the native implementation with a JavaScript implementation for better performance" was the goal at all. Rather, the goal seems to be "move away from a situation where one holdout browser (traditionally IE, more recently Safari/iOS) could scupper a new feature completely, and toward one where holdouts are just slower if they don't support that feature natively". There have been lots of examples of that strategy working - jQuery/QSA, asm.js etc.
Is that a misleading impression? Does Houdini have another agenda not covered by the article?
Re:Houdini: Maybe the Most Exciting Development in CSS
by philipwalton on Friday March 25, 2016 @04:05AM
(#11358960)
No, that is an accurate impression. The ultimate goal of Houdini is to give developers the tools to innovate; unlike the current situation were all innovation happens at the spec level, and devs have to wait (often years) for browser adoption.
Re:Houdini: Maybe the Most Exciting Development in CSS
by pcwalton on Thursday March 24, 2016 @11:37PM
(#11358362)
That's a reasonable use case for Houdini, yes. But I also think that if that's the goal CSS Paint and CSS Compositing should be redesigned...
Re:Houdini: Maybe the Most Exciting Development in CSS
by michaelchisari on Friday March 25, 2016 @04:36AM
(#11359038)
That's accurate, and totally reasonable. If the web is going to move forward, there needs to be a certain acceptance that older browsers should work, but they don't deserve to work well.
And definitely not as well as the latest and greatest.
Re:Houdini: Maybe the Most Exciting Development in CSS
by madeofpalk on Friday March 25, 2016 @06:25AM
(#11359320)
The target market is for library/framework authors, especially those wishing to make polyfills for future layout algos that haven't been adopted by everyone else yet.
It will be. And things like the CSS Paint API are based on APIs that are poor matches for GPUs (but are easy for browsers of today to implement). I expect that those who are looking for Houdini for performance reasons will end up quite disappointed.
More broadly, I have seen the "replace the native implementation with a JavaScript implementation for better performance" idea tried many times, and I can't think of a single time it's actually worked.