Has there been any discussions about central management of nonDNN JS resources?

For instance, I make heavy use of jQuery for custom skin behavior.  I ran into a problem however when a module used the library but referenced different version at a different location.  The two conflicted and broke the skin.  We need to put it a messy "use global content" option to override the module. 

It would be very helpful if DNN had better means for Managing this Content in the System.

(sorry if redundant or covered - Gemini not working)

Tom,

One fundamental weakness of using Pageblaster is it doesn't run on 100% of page views.  For errors, logins a few other cases where the module aren't triggered, your JS and external CSS files are not included.  Only by adding VB script to the skin was I able to get a consistent look and function.  That type of hack is beyond the scope of most admins.  It certainly diminishes DNN as a CMS.