And that's why they work. You allowed things like Google's and Jquery's CDN. If they blocked third-party absolutely then tons of sites would break.
You cannot use a bunch of addons which whitelist/blacklist content and assume that is remotely ballpark the same as outright blocking third party scripts. Those lists are heavily curated to make sure that stuff doesn't break.
I have found that most sites work (including the one hosting the article being discussed) well enough to read, or even completely true to the author's intent (depends on if CSS is self-hosted or on a CDN that I haven't whitelisted). I even find that often it is actually more pleasant to have a basic experience when CSS doesn't load.
Sites that require me to allow a lot of third-party scripts and content to work force me to weigh the expected usefulness of the content vs the scumminess of the site. The creepier and more plentiful the third parties are, the more likely I am to press the X...
I very rarely have to allow Google and JQuery in my day to day browsing.
I don't find that to be so. I use Firefox with AdBlock, NoScript, RefControl and Disable WebRTC. In NoScript, I've flagged third-party ad servers and trackers as untrusted. In RefControl, I block third-party referer by default. I use private browsing mode, and accept third-party cookies from visited sites, but all cookies are deleted when Firefox closes.
I do allow useful content from third-party scripts. But that doesn't include crap from Facebook etc. And it's very rare that I need to enable other third-party scripts to get what I want from sites. If there's something truly evil that I want to read, I fire up a LiveCD VM.