Web browser blogs
Nearly all the main players in the browser world have their own blogs and while they might range in their usefulness they can give you an interesting perspective on the vendors ideas of themselves.
The obvious missing link above is from Apple, is the WebKit blog better for Apple than having their own? The fan-boys run Safari anyway. The WebKit blog focuses mainly on the visual elements they add and improve (CSS transitions etc), with the more tech elements (Eg. JavaScript performance) listed but given second billing.
At Mozilla, Firefox is just a category, it's not got it's own blog. Recently it's very focused on security and updates.
Chrome's blog is really new, although there is an older blog for Chromium concentrated on performance and stability
Opera's blog re-forces their position, unfortunately. The underdog's blog is all about getting the word out from their tight following, the tech elements play second fiddle. The Opera developer area is great though …
When IE6 is dead...
Every web-developer on the planet, is waiting for the day we don't have to do anything for IE6. Nevermind creating scaled back versions for it, I'm talking about the day we don't even think about.
Wouldn't that be great.
Heres a quick list of the kind of simple CSS selecters we'd finally get to use;
Child selector
div > p - A little one to start with, but how useful. > matches only elements that are the direct children of the parent,
Sibling selector
p.bill ~ p.ben - If .bill is before .ben then the rule is true. Not the same as '+'.
Attribute selectors
div[aria-live=assertive] - Useful for more than just for input elements. and if you can find a use for them, advanced attribute selectors allow you to part match stings,
Multiple classes
div.big.red - Sure you can often get away with using these right now, but little risky no?
Inline-block
display:inline-block - IE6 lets you do this on inline elements, but being able to put these on a div cuts down those 'floating' headaches. Use with a liberal dash of -moz-inline-box or -moz-inline-block in FF2.
First-child
:first-child - If you can resist the temptation to move these around with JavaScript, it's the end of putting a class on your first navigation element... now if only last-child worked.
The day IE6 is dead can't come soon enough
Pay homeage to QuirksMode.org for the above research.