Live data from Hacker News

A Shocking Truth About CSS

blog.twoalex.com

1–10 of 70 posts

Re: A Shocking Truth About CSS

#4
Can anyone point to where this is required by the css specification? Or is this an implementation detail? The reality may be that all the browsers do it this way, but why couldn't someone add some more smarts to choose selectors based on selectivity, just as a SQL query planner would?

Re: A Shocking Truth About CSS

#7
post #4

Can anyone point to where this is required by the css specification? Or is this an implementation detail? The reality may be that all the browsers do it this way, but why couldn't someone add some more smarts to choose selectors based on selectivity, just as a SQL query planner would?

It’s quicker to walk up a DOM tree than it is to walk down - that’s the root reason why browsers have all implemented it this way.

Re: A Shocking Truth About CSS

#9
post #6
post #3

(from the header:) The Two Alexs Alexes? Alex's? Alexi? Alexim? In hackanonical form, Alexen. As in oxen, vaxen, boxen.

"Alices", by analogy with "codex".

It's a Greek name, so I'd go with that for plurals, rather than German or Latin templates.

Re: A Shocking Truth About CSS

#10

The "Two Alexes" are just discovering (Feb 2010) what Steve Souders explained in detail at http://www.stevesouders.com/blog/2009/06/18/simplifying-css-... [which is probably the site you want to visit on "How CSS strategies affect site performance"] (June 2009).

Being "scooped" by a mere 6 months, on a 10 year old technology doesn't really make their realization dated.

It's new to me, and I bet it's new to most news.yc-ers.

Post reply on HN