Picasso never said that. Jobs misquoted. But the real quote from T.S. Eliot is better: “Immature poets imitate; mature poets steal; bad poets deface what they take, and good poets make it into something better, or at least something different. The good poet welds his theft into a whole of feeling which is unique, utterly different than that from which it is torn.”
Well, but other subscribers paid as much as you but may not be using Youtube as heavily. When they do use Youtube, they want that fast connection, but in aggregate they use less capacity because they are less frequent users. Charging Youtube is one way to account for this difference in usage. Charging consumers based on aggregate usage (like mobile carriers now do) would be another way.
so all you are saying is that some people pay for (N gigabytes per month) and actually use N, while others pay for the same plan but only use a fraction of N?
I'm referring to typical home/business service where you pay for X downstream/Y downstream, not aggregate usage. Almost everyone will use the full bandwidth at some point (just watch just one video) but some people use it more frequently.
Granted, Andreesen was talking about mobile where pricing is N gigs/month, but even that structure might not capture true cost. It also depends when the user uses that bandwidth. During peak hours, capacity is short and end-user Quality of Service might get degraded to accommodate. Rather than complicating end-user pricing with these issues (like charging $Y for X bits at ZZ:ZZ PM), it might make sense to charge the content providers.
Who knows what the best solution is. Maybe it's charging content providers, maybe end-users. The point is that it's not a good idea to have the government set a one-size-fits-all solution.
The tests were run with:
Java OpenJDK 1.7.0_09 Resin 4.0.34 Play 2.1.0