Yeah? How about money?
As a comms engineer, I too think about the technical implications of this.
But you have to remember that the people who push for the abolition of net neutrality are mainly the finances guys, i.e the ones responsible for bringing as much money as possible to the company. And when you put yourself in their shoes, all of a sudden you get dreams of Comcast turning the Internet into the same kind of market it has in cable television. And you very quickly forget about QoS, bandwidth, latency and the job of "delivering the bits" and just think in terms of profits. You wouldn't know what most of those terms mean anyway...
But more generally, slow-loading websites make the ISP's service look shitty. There's almost no cost for them to just QoS the low-bandwidth stuff up and it makes people think their service is better.
Exactly, so people will just leave that ISP and sign up with one that doesn't throttle traffic. Except most people have only one ISP in their area. Yay free market!
In a truly free market, there would be one company that owns everything, including infrastructure. Not a world I'd like to live in.
Why should Netflix pay disproportionately more for its bandwidth than a non-video streaming service?
You can't think of a few sites and services that TV cable providers would like to slow down? The issue isn't that the general web will get slower, but rather that cable companies will become the arbiters of which services survive and prosper.
This reminds me of when the TSA took over airport screening after 9/11, over the belief that only a government agency could screen passengers securely. The net effect was longer lines, more expensive travel, less rights for flyers (ie either you get a body scan or a pat-down, and no more liquids on flights), and in general less happy travelers.
Think about it, the only reason Comcast is doing all this is so they can charge premium fees on certain services. If you don't allow them to do so (which is very easy to enforce, as customers can report such pricing policies), they have no incentive to be against net neutrality.
This is why the current status quo has worked for so long: ISPs have no way to legally make profits out of "premium" traffic, so they (generally) don't apply outrageous QoS measures. Money is the only incentive, and removing that incentive solves the problem without the need for active policing.
And because they weren't allowed to charge extra for "premium" traffic, they essentially switched over to the over-subscription model in order to make profit. The tighter you squeeze, the stronger it oozes out the sides. And never in the place or way you wish it would!!
(I was tempted to downvote you for your persecution complex, but that would only validate it so I'm torn.)
Regardless, the point is that QoS exists to keep non-video traffic from getting trampled out by video traffic. Video traffic is such a disproportionately large amount of total Internet traffic that virtually the only services that would be significantly impacted by being in the "slow lane" are video services. The links wouldn't even be saturated in the first place without video traffic.
EDIT: Also wanted to add that congestion is almost guaranteed with adaptive bit rate streaming. Netflix will use as much bandwidth as is available up to like 9 mbit/s.
A citation is needed here. Somehow consumer ISPs got along for 15 years without "permanent congestion".
EDIT: Just wanted to clarify that 50% is a number I pulled out of my ass. The general point is that the percentage of users who stream video online on a regular basis is increasing more quickly than the economics/logistics allow the ISPs to perform network upgrades.
This is another citation needed point. Bandwidth consumption has always increased over time, as has the performance per dollar of routing equipment.
There are exceptions of course. Older OSes have ridiculously small TCP receive windows, and older TCP congestion control algorithms have trouble filling the pipe. But these shouldn't really be the main problem these days. It doesn't apply so much for streaming either, because modern streaming protocols such as MPEG-DASH will select a lower bitrate stream if they sense congestion.
I think all this talk of the "slow lane" is a bit tinfoil-hat. Companies like Comcast have no interest in slowing down web site traffic; in fact they do a lot of QoS to make web browsing faster and more responsive. This type of traffic (DNS, HTTP requests, online gaming, etc.) tends to get put in a high-priority QoS class: the data transmitted is often small and it greatly improves the user's experience. ISPs have a huge incentive to make this type of traffic as responsive as possible; and given the low bandwidth requirements, this should definitely be possible. It makes their service "feel" faster to the customer and it's the right thing to do for the customer.
Video streaming services are another story. They don't need to be responsive because they pre-cache a lot of data; in fact the right thing to do from a technical perspective is QoS them into the basement. Video can handle this; it's high bandwidth and low latency. The thing is, streaming video accounts for about 80% of peak Internet traffic. A small percentage of users (~30%) are starting to overload the ISP's last-mile networks with video traffic.
The types of high-bandwidth scenarios that the ISPs will be pushing the "fast lane" on are going to be almost exclusively video streaming services. Video streamers have had to pay CDNs for years anyway if they wanted their videos to stream quickly. The idea is that because these services have such a disproportionate effect on bandwidth usage, they need to contribute economically to avoid a tragedy of the commons [1] situation. Your average website or app that's not pulling 1.5+ mbit/s over an extended period of time is likely going to be fast regardless because it's in the ISPs best interests to make it that way.
[1] http://en.wikipedia.org/wiki/Tragedy_of_the_commons