Sometimes I still browse Digg (it's different now). Since the last Firefox update from a week ago which disabled Symantec certificates the site doesn't work anymore. I bet the day Chrome disables Symantec certificates they will immediately notice and fix it.
It's sad that in one week not even one of their people opened it in Firefox, and not many of their users either (there was just a couple of mentions on Twitter about this issue)
My 7 year old audio interface (E-MU 0404 USB 2.0 for who cares) started making BSODs after upgrading from Windows 8 to Windows 8.1. The latest manufacturer drivers were for Vista.
I reported it on answer.microsoft.com. They asked for a crash dump. Complied. Another non-ms person analyzed the crash dump and suggested that it's USB 3.0 related. Disabling that in the BIOS solved the issue.
But the MS guys kept on going. A few weeks later, a reply that they managed to get their hands on a similar device (!!, cost about $200), but they couldn't find a driver, so they asked for mine. Pointed them to the online driver location (hidden on manufacturer site). Some time after that they commented that they managed to reproduce the BSOD. A few months later they released a fix (into Windows).
You can also increase the priority of your thread/process. Works pretty well. On Windows, you can also mark your thread as being audio related and latency sensitive (Multimedia Class Scheduler Service)
Using formats which became less popular and well supported can be considered bit-rotting.
For example, having .PCX files in some project today instead of .PNG could be considered a form of bit rotting, because less and less tools support .PCX
It seems the consensus is that new features like "auto" are not wanted:
Principle 13: Unlike for C99, the consensus at the London meeting was that there should be no invention, without exception. Only those features that have a history and are in common use by a commercial implementation should be considered
It's sad that in one week not even one of their people opened it in Firefox, and not many of their users either (there was just a couple of mentions on Twitter about this issue)