I agree if you’re already using Spotify to listen to podcasts. But if you’re not, you’d definitely notice a move to Spotify Exclusive because you’d need to have two podcast apps.

Plus your experience would degrade substantially, since before, you could have a music play queue for times you want to listen to music, and a podcast play queue for times you want to listen to podcasts. Now you'd have to manually push things in and out of a single play queue.

Why do people actually do that?

The "You name a critical .js bundle something related to ads" point is something toward which I'm particularly unsympathetic. The fact that most ad blockers (a) are whitelist-based and (b) contain blunt-edge/naive implementations leads me to believe that false positives are the problem of the ad blocker developer and ad blocker user, not the developer of the website.

If Joe or Jane developer of Acme Demolition Inc. names a Javascript file `ad_main.js`, the burden of resolving the my-ad-blocker-is-blocking-this-file problem is not on them.

This is why I've yet to find an ad blocker that I would recommend to anyone without web development knowledge.

And I'd argue the opposite, based on desire paths.

People will bend the Web to suit their goals. You as a web dev with a need for ads revenue focus on that. Me as a web user with a need for information and pathological hatred of anything distracting, focus on my needs. Users with visual and motor disabilities (I support a community of same) are quite actively thwarted by many revenue-positive factors.

My fix for a bunch of Web gunk is to have a default set of client-side CSS that kills, well, a bunch of crap. Flyovers, modals, interstitials, fixed header/footer elements, and a slew of other stuff. Ello's front-end guy pretty understandably said it voided my warranty for the World Wide Web. And he's not wrong.

But man does it make things suck ever so much less.

Which gets to the point: much of the stylesheet is glob-match patterns on descriptors that are frequently annoying as fuck-all. Which was why I'd showed it to him. That sheet, or others like it, are going to be in the client world, and soon, and if you're putting flyover and modal keywords in your selectors, they're going to get blocked.

Yes, it's an iterative arms race. Your turn.

(And: ultimately the solution is to fix the revenue/compensation model for published works. Online and elsewhere. That'll take a while, but it'll also fix very nearly everything wrong with the present iteration of the Web.)

I'm a heavy ad blocker user, and I have never needed to whitelist anything myself. All the adblock lists I've ever used consciously avoid anything so generic it'd catch ad_main.js on J. Random Website. (Hell, if anything they undercatch—I have several rules for things which are ads and aren't blocked.)

Tower is, in my opinion, the best and most full-featured Git GUI. Having used it within multiple teams, I've found that it helps users understand what's happening under the hood (esp. regarding remotes). Unfortunately, the author seems to be a Windows user and Tower is, as of today, only available for OS X.

Find it here: http://git-tower.com

Looks awesome! Great idea and execution. I tweeted it at Jalen Rose and Bill Simmons.

Minor things:

- You're throwing a bunch of log statements right now. Might be taking down the javascript in IE (I didn't see if you wrapped `console.log`).

- Remember, `this.$el` can replace `$(this.el)` (gotta love those convenience methods, I see you're using `this.$(selector)`).

- Also, UnderscoreJS provides `_.isUndefined` and `_.has` which is a little nicer than the `typeof foo.bar !== undefined` test.

Wow, thank you. To be honest I'm quite new to js, especially backbone and those other util libs like underscore. Really appreciate the CR, will fix shortly.