I'm currently working on a couple of government projects that must adhere to the latest accessibility standards, and they include this little doozy: no javascript.
Completely, and utterly false. WCAG 2.0 (i.e., the latest accessibility standard for Web technologies) does enlist Javascript as a supported technology, and provides several techniques to successfully meet the criteria.
As of now, he's got already 26 forks, so he's been cloned several times.
But what will be impressive is having merges (via pull requests) accepted into the master branch. Crowd-sourced gene therapy (or mutation) anyone?
Remember when it was ok to use a "b" tag, and no one scoffed? How about table layouts? It's funny, the new standards aren't always better.
If you still think it's actually not better, sorry, but you should have 10 blind persons hit you with their canes...
It also affects the authplay.dll component that ships with Adobe Reader and Acrobat 9.x for Windows, Macintosh and UNIX operating systems.
Who has been asking for all these electrical applications? I keep reading about the freakin' "ELECTRICITY!!!" and am just not impressed. I wouldn't trust anyone's electrical platform with my company's tasks.
As many people have mentioned, once the electricity goes down, no more electric anything. I want my apps, my tasks and my work all under my control on my local manpower. There are uses for electrical applications but to rely on them for business, private tasks or to store anything that lack of access to would cause a work stoppage is a bad idea.
Now... get off my lawn!
The Tao is like a glob pattern: used but never used up. It is like the extern void: filled with infinite possibilities.
