I think it's not very exciting at all. Browser support for Houdini will be a new issue in the future if they manage to release anything.
Houdini: Maybe the Most Exciting Development in CSS
11–20 of 63 posts
Re: Houdini: Maybe the Most Exciting Development in CSS
#12Great! But sadly, I must keep working with IE8 compatibility. Government related clients update at glacial speed...
Re: Houdini: Maybe the Most Exciting Development in CSS
#13Quick question, what's to stop someone from reimplementing, say "float: right" to also spin up a banner ad? That is, this sounds great in principal but much like Microsoft's Tay taught us, the internet is full of *-holes.
Re: Houdini: Maybe the Most Exciting Development in CSS
#14Quick question, what's to stop someone from reimplementing, say "float: right" to also spin up a banner ad? That is, this sounds great in principal but much like Microsoft's Tay taught us, the internet is full of *-holes.
Well that's already possible now just by reading the CSSOM and patching new things into the DOM like how the article described the current state of affairs. If you just want to shunt another banner ad in there, that's not something that will hurt performance too much.
Re: Houdini: Maybe the Most Exciting Development in CSS
#15Quick question, what's to stop someone from reimplementing, say "float: right" to also spin up a banner ad? That is, this sounds great in principal but much like Microsoft's Tay taught us, the internet is full of *-holes.
I'd expect that anyone who has access to the page/app enough to extend CSS to spin up ads would also have enough access to the app/page to just put ads on it anyway, in much easier ways.
Re: Houdini: Maybe the Most Exciting Development in CSS
#16Seems like a band-aid for CSS, which needs to go away. Styling the DOM in the fashion we have been for the last 15+ years needs to end. JavaScript has evolved, but we still need to use LESS and SASS and Modernizr and other tools.
CSS doesn't need abstractions. It needs to be replaced.
Re: Houdini: Maybe the Most Exciting Development in CSS
#17I think it's not very exciting at all. Browser support for Houdini will be a new issue in the future if they manage to release anything.
XKCD 927.
Re: Houdini: Maybe the Most Exciting Development in CSS
#18Seems like a band-aid for CSS, which needs to go away. Styling the DOM in the fashion we have been for the last 15+ years needs to end. JavaScript has evolved, but we still need to use LESS and SASS and Modernizr and other tools. CSS doesn't need abstractions. It needs to be replaced.
It does not need to be replaced, and it's highly impractical for it to be replaced since it's such a core part of all web browsers that's not going away anytime soon.
Are you suggesting we style with JavaScript?
Re: Houdini: Maybe the Most Exciting Development in CSS
#19Seems like a band-aid for CSS, which needs to go away. Styling the DOM in the fashion we have been for the last 15+ years needs to end. JavaScript has evolved, but we still need to use LESS and SASS and Modernizr and other tools. CSS doesn't need abstractions. It needs to be replaced.
It does not need to be replaced, and it's highly impractical for it to be replaced since it's such a core part of all web browsers that's not going away anytime soon. Are you suggesting we style with JavaScript?
Flash was also once a core part of the web browsing experience.
CSS is a big warty blob, and a relic of the "semantic web."
"Styling with JavaScript" is probably too verbose of a solution, but it's one option.
Re: Houdini: Maybe the Most Exciting Development in CSS
#20> This subset will only include properties that can be read or set without forcing the rendering engine to recalculate layout or style (for example, transform, opacity, scroll offset). I'm frankly skeptical of most of Houdini, but I'm especially not happy with this one. This is baking the limitations of current browser engines into the platform for all time. The provided justification seems pretty flimsy to me, becau…
Don't just complain about it on HN, tell the developers directly (via GitHub or otherwise).
A fair point, but pointing out a perceived flaw on Hackernews often leads to good discussion, and is sometimes followed by the authors themselves. I can see both sides of it, but I'd personally like to start it here then carry it over to filing an issue afterwards (if it still feels it has merit).