That was fast! 
thank you. I quite like the metaphor of the local maximum. Can certainly be the right place to be sometimes.
It feels like a common use case to add additional attributes to script tags like django-js-asset does, would you not want to see that added to Django? You called it a hack earlier, but it seems like it’s a widely-used one and possibly API-compatible hack, so why not take it further / do it in Django itself?
Or if not by changing the implementation in Django, perhaps mention in the Django docs “here is a way to add attributes which would help for use cases X, Y, Z”?
There are discussions going around on whether the Django admin can and should be considered a CMS (my opinion is that it is and should be) but as long as there isn’t a broad consensus that the Django admin should evolve I’m not sure if a rework is in order or not.
Could you share some of those discussions? Personally I think there’s room for improvement on Form.Media regardless of whether those improvements would be beneficial for the Django admin or not, but keen to have more context here to understand what others requirements people might have in mind.