The drupal.js dependency is another subject, do we want the settings to create the global [D|d]rupal object, or do we want to create it anyway, all the time, even if it's empty? I guess this bit is up for discussion, we really need to find a way to remove the $.extend thing anyway.
Drupal.settings changed to drupalSettings:
In order to reduce the dependency on jQuery (and in particular the need for deep object merging like with
Drupal.settings object was given its own top-level namespace, namely
drupalSettings. For legacy reasons, the
drupalSettings object is still copied over to
Drupal.settings, but the settings are no longer merged by means of
PASSED: [[SimpleTest]]: [MySQL] 41,484 pass(es).
FAILED: [[SimpleTest]]: [MySQL] 41,383 pass(es), 102 fail(s), and 105 exception(s).
PASSED: [[SimpleTest]]: [MySQL] 41,480 pass(es).
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch core-js-remove-jQuery-settings-1760548-22.patch. Unable to apply patch. See the log in the details link for more information.
PASSED: [[SimpleTest]]: [MySQL] 41,293 pass(es).