I don't think Mac users are smug. I think they state a known fact. There are fewer exploits to Macs. That doesn't mean there are fewer vulnerabilities. Yes OS X and Windows share many of the same vulnerabilities. Yes Windows has implemented some great security features. But all of that has done little to stem the large number of exploits to Windows because it has a much larger market share.
Someone (I think it was Charlie Miller) put it best (paraphrased): You can stand in a war zone or you can be thousand of miles away. Running Windows is standing in a war zone. Running a Mac is being thousand of miles away.
You seem to be unhappy about this asymmetry. Even despite Microsoft doing all that work it remains. The real interesting question will be if Apple can respond to being a popular target better than Microsoft?
OS X has used sudo since the beginning. It's long been suggested practice not to setup your day to day user with Admin rights. There's no real problem there because anything you need admin rights to do prompts and you can put in the admin username/password, basically GUI sudo.
Example of the long standing suggestion to not use accounts with admin access dating back to 2006. I could probably find older ones if I felt like going past the first result on google:
http://www.macgeekery.com/tips/security/basic_mac_os_x_security
I can guess why they didn't put those keys in. Possibly so that people don't hit them on accident. I know on some laptops I've had with them I've hit them on accident from time to time.
I'm primarily a vim user so I don't miss the insert key or delete, though I have used Fn+delete to get forward delete a handful of times.
The eject button works for me before the OS boots. It takes a bit before it's active but then it usually takes a bit before a hardware eject button works unless it's purely mechanical as a lot of laptop eject keys are.
Not sure about how the volume keys work. I haven't tried it and don't feel like rebooting right now to muck with it.
The ash from coal plants is radioactive. Coal has low concentrations of radioactive elements in it. When you burn the coal the radioactive elements are among the ash and are at a higher concentration of the ash than they are of the source coal.
http://www.epa.gov/rpdweb00/tenorm/coalandcoalash.html
http://pubs.usgs.gov/fs/1997/fs163-97/FS-163-97.html
A lot of the commentary about radioactivity and coal plants come from this Scientific American article:
http://www.scientificamerican.com/article.cfm?id=coal-ash-is-more-radioactive-than-nuclear-waste
Many people read the headline of that article and didn't really bother to read the article. The argument that Scientific American makes is that a coal plant puts more radiation into the surrounding environment than a nuclear plant. The nuclear waste is still obviously more radioactive than the ash. However, the nuclear plant carefully controls their waste and materials.
In both cases the radiation released is low and not a health risk.
Clearly the editors have a time machine and they knew that the 3rd explosion was going to happen. This also explains the constant dups due to editors becoming confused about the ordering as time as they zip around.
I don't know about the person you're responding too but I actually routinely get better latency via IPv6 tunneled via Hurricane Electric than IPv4 through my own ISP.
Fact of the matter is that IPv6 should be slightly faster since the routers don't have to recalculate a CRC for every hop. HE has multiple tunnel broker servers around the world. So you can pick one close to your network and the only CRC latency you'll eat will be the hops between you and the tunnel broker site.
Example:
--- leguin.freenode.net ping6 statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 205.932/215.147/262.156/16.624 ms
--- leguin.freenode.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 280.228/329.908/374.605/31.503 ms
And I just picked a random IPv6 host that I knew I could target the same machine via either network. I didn't dig around to find a machine that gave me better latency via IPv6 than IPv4.
At least pipe it to view: curl http://tech.slashdot.org/story/11/02/14/2357242/ | view -
Or you could use -R on vim (but view is the same thing): curl http://tech.slashdot.org/story/11/02/14/2357242/ | vim -R -
So you don't get bitched at to save it when you're done.
When it is incorrect, it is, at least *authoritatively* incorrect. -- Hitchiker's Guide To The Galaxy