Second, I whitelist sites for javascript. There's nothing absurd about that. Honestly, I can't believe people run any and all JS on every random page they land on.
For most sites that sounds like a good idea, but this is a Javascript project. The number of people interested in a Javscript framework that don't have Javascript enabled and are still befuddled when things don't work correctly must be vanishingly small.
Isn't that actually the opposite argument? If you are an expert in that field, you should understand how to degrade gracefully. Besides, you might not know that the project is about javascript until you read the (blank) page.
Citation needed.
The technologies have evolved... Why are you trying to keep us in the stone age? Or why do you expect backwards compatibility?
Which is why the HTML5 spec explicitly mentions disabling scripting?
"6.1.2 Enabling and disabling scripting
Scripting is enabled in a browsing context when all of the following conditions are true:
The user agent supports scripting.
The user has not disabled scripting for this browsing context at this time. (User agents may provide users with the option to disable scripting globally, or in a finer-grained manner, e.g. on a per-origin basis.)
The browsing context's active document's active sandboxing flag set does not have its sandboxed scripts browsing context flag set.
"