The number of skilled Indian workers in Germany has increased to 1.3 lakh from 23,000 a decade ago

Govindan says CPI(M) does not require members to seek prior permission to write a book, though he emphasised that consultation with the party should occur before publication

Their tearful reunion touches many, as they witness the heartbreak of lost connections. We celebrated the previous election, but many who participated then are no longer with us, says a survivor. District administration designated three polling stations for the survivors, two at Neelicappu and one at Meppadi

GSK will keep its existing portfolios while entering areas like oncology, said company officials at its centenary celebrations

Front-end developer Steffan Williams of Gridinator fame digs into some of the rendering inconsistencies across various browsers when dealing with percentage-based widths. Now, I don’t think this is a real problem for flexible, grid-based layouts or properly responsive designs. Some of these rounding issues won’t necessarily manifest themselves in your work, or at least not quite as noticeably.

I was, however, emphatically raising my fist in the air when I read this:

While I’m well aware that things don’t have to look the same in every browser, it just seems to strike me as odd that CSS3 features keep getting touted on the front of browser homepages, and yet something as fundamental as a percentage would be rendered incorrectly (or, rather, not as well as would be expected).

Emphasis mine. Much of the behavior Steffan notes was outlined by John Resig in 2008, nearly three years ago. There are some incredible inconsistencies at play here, and designers really shouldn’t have to shoulder the burden of working around them.

In short, some broad consensus between the different rendering engines needs to be reached—and if it comes at the expense of pushing the Next Hot Bleeding-Edge Experimental Sexy CSS3 Feature™ to market, I’m all for it.

Having a bit of a problem with my laptop lately, and thought I’d write up the problem in case it’s affecting anyone else:

So my MacBook Air (mid-2009, OS X 10.8.3) When my computer wakes from sleep, it doesn’t immediately reconnect to my wireless network. What’s more, if I open up the wireless menu in OS X’s menu bar, it doesn’t show any networks nearby. Zip. Zero. Zilch. It’ll scan for new networks repeatedly, but won’t see a single one.

But here’s where this gets really, really annoying: if I open the Network panel in System Preferences, all nearby networks are immediately visible without delay.

Given the weird inconsistency between the two menus, and that I can reproduce this issue consistently, I figure this is a bug: either with 10.8.3, or with my aging little laptop. Either way, I’d love to fix it. So if you’ve come across this problem and know how a workaround, suggestions via email or Twitter would be most welcome.

Update: Charles Gaudette suggested on Twitter that it might be a couple , and pointed me toward a page showing how to clear out corrupted plist files. Deleting the com.apple.network.identification.plist and com.apple.airport.preferences.plist files seems to have done the trick—thanks, Charles! And thanks to everyone else who wrote in or twittered suggestions at me.