A Shocking Truth About CSS
blog.twoalex.com
A Shocking Truth About CSS
1–10 of 70 posts
Re: A Shocking Truth About CSS
#211:44:33 AM Alex K: that makes it sound like it may not be worth huge optimization?
11:44:46 AM Alex M: no, not really
Re: A Shocking Truth About CSS
#3The Two Alexs
Alexes? Alex's? Alexi? Alexim?
In hackanonical form, Alexen. As in oxen, vaxen, boxen.
Re: A Shocking Truth About CSS
#4Re: A Shocking Truth About CSS
#5Re: A Shocking Truth About CSS
#6(from the header:) The Two Alexs Alexes? Alex's? Alexi? Alexim? In hackanonical form, Alexen. As in oxen, vaxen, boxen.
Re: A Shocking Truth About CSS
#7Can 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
#8Re: A Shocking Truth About CSS
#9Re: A Shocking Truth About CSS
#10The "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).
It's new to me, and I bet it's new to most news.yc-ers.