Here, speaking as a public safety official? Neither.
If other public safety officials in other areas have problems with either of them, they need to assess how they're communicating, and more importantly, what they're communicating.
As an example for your first point, the local police had a stand-off with a mentally disturbed guy with a gun hiding in a wood pile behind someone's house in a neighborhood in my city this past fall. It's pretty uncommon around here. Because the call was in a different county, but still just outside city limits, it was dispatched to that county police first. However, the city was dispatched as well because it could easily spill over into their jurisdiction. The state police were also dispatched.
The city arrives first, they are on an analog repeater system.
The neighboring county arrives second (this stretches to the far north border of their jurisdiction so their arrival was delayed), they are on a EDACS Provoice system.
The state police arrives third, they are on the APCO 25 system.
Before they even have time to assess the situation, get everyone on the scene, establish a perimeter, get a plan of action and call out the special response team, all communications are going over the city's analog primary dispatch channel (where I was listening) and traffic was being relayed manually between three dispatch centers because nobody could directly talk to each other.
Thankfully it ended without incident, but my point here is sometimes they don't have the time or ability to coordinate on anything but the primary channels, even if they have the capability, it's of no fault to public safety per se. Just because they could and should doesn't mean it's always practical or that they have any inclination to keep things sensitive for the sake of keeping scanner listeners away when seconds count. Had the guy had a smart phone on him (more likely than a scanner), it could have ended much different, made negotiations much harder, and someone could have gotten seriously hurt.
If drug dealers are keeping ahead of the cops because they're able to hear when the cops are coming after them, one argument (yours and some others) is that the concept of a live audio feed - or more precisely, the fact that RR hosts the feed - is at fault. Another argument is: Why are the cops telegraphing their punches? Why isn't the drug unit operating on a channel that is either (a) encrypted or (2) in the kind of allocation that RR bans from feeds by policy?
I still maintain that while the technological advances might make it more accessible, there is still no more dire urgency and danger in having public safety comms accessible via the Internet, than there has been for the past ~50 years using scanners and other tunable and non-tunable receivers. If that goes against your or anyone else's opinion or viewpoint, so be it.
I can summarize my response by saying that this site does nothing more than make what was a relatively small and unknown problem 5 years ago a gargantuan problem today, especially considering there are now real listener numbers shown to the public that indicate how many people are listening in at any given time. Anyone in a position of power only needs to glance at their area's feed page and cringe with anxiety when more people are listening in than the number of officers on duty, and at any given moment could negatively affect the outcome of any serious situation to life. It's unfortunate, but true. With real numbers it does nothing but make public safety officials uneasy, making them feel more compelled to react, particularly in ways not favorable to the hobby. One thing RR.com could do today with very little effort is disable the listener counts and keep them private. I can't see why anyone would argue with that, but I think that cat is already out of the bag.
In addition, it creates an environment among public safety where anyone with a smart phone device becomes a person of automatic suspicion, or added suspicion to an initial reason. That isn't good for a smart phone owner. Unfortunately until something gives, this problem isn't going away.
