That's fine, it's only your users after all.
> No, you shouldn't. You should focus on stuff that matters to users, not existential internet security holes.
If you can fix a hole until that hole is plugged in a more permanent fashion then I think that you should.
> FTFY "A safe, but impractical and productivity-destroying aproach..."
Entirely practical and with minimal impact on your productivity. If you can find the time and expend the effort to build a product to begin with then you can certainly find the time and expend the effort to make a conscious decision about things like this.
It matters enough to me that it affects my choices with respect to which parties I deal with on the internet and I sure hope I'm not the only person that thinks like that.
And every time some user gets their day ruined by some formerly javascript widget hosting domain that got transfered to a new and malicious owner there is a bit more evidence to support that that approach is the right one.
From the end users point of view as long as it works the two solutions are identical and if you're serving up megabytes of content anyway what's the big deal about serving up some scripts directly as well?