Your third paragraph was enlightening and explained your position reasonably well. I'm not sure I'm convinced, but it seems like an interesting discussion.
I feel obliged to downvote you because of the first two paragraphs, why did you add them? You were trying to refute what you considered an "accusation of arrogance" with the most arrogant opening paragraph possible?
Not a windows user, but the same applies to gdb. What is your proposal? If you're currently debugging a thread, breakpoints are disabled for other threads? That really doesn't seem like what people would expect by default.
I think you're forgetting that resources cannot be shared if they're marked private. You cannot get account_statement.js from your shared cache, it has to be unique to you.
I'm not a privacy defeatist, but I am a fingerprinting defeatist. Here's why: I don't think it's realistic for caching and anti-fingerprinting to co-exist, and given those two options users will always pick the former because the latter would be perceived as slow.
The classic example is:
<script src=foobar.js>
Where foobar.js just returns something like "var id=0x1234567", the user who doesn't want to be fingerprinted cannot cache this script because it could be uniquely generated.
I feel obliged to downvote you because of the first two paragraphs, why did you add them? You were trying to refute what you considered an "accusation of arrogance" with the most arrogant opening paragraph possible?