Skip to main content

Why I Do Not Support Net Neutrality

It's simple, actually:

1. Nothing is free (as in beer)
2. Usually, items that are perceived as free (highways, the Internet, Welfare, Medicare, public safety services, etc.) are paid for by the government
3. The U.S. government gets its funding from its citizens--that is you and me
4. I indirectly (through taxes or through "add-on" cost-recovery fees from corporations) do not want to pay for someone else's Internet service.

If someone wants a faster pipe (or improved routing), that's fine. They can pay for that pipe. But I don't want to pay for their faster pipe. Also, with net neutrality, there's no incentive to improve delivery. If I'm Sprint, Verizon, or AT&T, why would I improve my service? There's no financial incentive. With Net Neutrality, I can't charge more for it. The Internet is not free (as in beer). It's no more free than making a phone call or getting cable TV.

Uncle Sam may have built Arpanet but the communications firms of this country build the modern-day Internet (at least within the U.S.). If I build a building, I should have a right to sell condos in that building for whatever I want. If the market for condos supports what I'm charging, that's great. The government should not be allowed to step in and say, "oh, BTW, every one of those condos has to be priced exactly the same...oh, and they can't exceed this ceiling". That's BS. I made an investment in my building and expect to realize a return on that investment. Otherwise, in the future, I will choose not to build that building and as a result, someone might not have a place to live. (as an extreme example)

This country was built on capitalism and self-reliance. We've grown into a group of complacent, handout-seeking, egalitarians. Save me! Save me! It has to stop. The government's role in this country should be to maintain individual rights, provide law and order, and maintain property rights. Otherwise, the government controls or has a hand in too much of our daily lives. The framers of our constitution never intended Uncle Sam to serve as a bedside nurse--they intended Uncle Sam to provide an environment of freedom and opportunity with a few rules such that its citizens could create and provide for themselves.

Let capitalism and economics do their thing. They usually work things out. Freedom isn't free.

Update 01/23/2007: Several of the founders weigh in against Net Neutrality.

Comments

Jeff Hunsaker said…
This is no different than the existing phone system. Both the sender and receiver are charged. The sender pays for the call but the receiver has to at least pay for local service to even accept calls.

Also, capitalism will once again come to the rescue if for example, AT&T charges the recipient of traffic: the commercial recipient will pay for both. Think Amazon will disallow traffic to reach their servers? Heck no. This might be tough on the little guy but let's remember this isn't service or no service; it's mediocre or enhanced service.

With paid monthly service, everyone will get some sort of baseline feature set. With "basic", I can traverse anywhere on the Internet I choose but perhaps not with blazing speed. For $20/month...I'm just fine with that. I experience this today with [evil] SBC. I could be $40 for double the speed but it's not that valuable to me.

Now, if I'm Amazon (or some other Web 2.0 firm ;-), that probably won't cut it. So, I pay AT&T more to get a faster pipe. Firms do this today in the form of leased lines.

I'm continuing my research and hope these analogies are accurate. That said, it has been my experience the path of rational economics, capitalism, and open markets rarely parellels with the sentiments of MoveOn.org and the democrats in Congress. MoveOn.org and the democrats in Congress remain the strongest net neutrality supporters. Not that the republicans have it figured out either but this situation alone raises the hair on my neck.

Popular posts from this blog

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki...

Switching the Parents to Ubuntu...?

I spent a half hour or so recently on the phone walking my Mom through a technical issue. Tentatively, I diagnosed her issue as a hard drive failure. She brought it over on her last visit and sure enough, the Dell XPS 450 from circa 1999 sounds like a bad coin-operated laundry at full capacity. I was aghast to discover she's running Windows 98. Ugh. Also, her recovery disk is just that--for recovery. I don't believe I'll be able to re-install Win98 on a new hard drive. That, coupled with the end of Microsoft (and Dell) support for Win98, got me thinking about Linux. (and she's not intense about her computing needs...and she doesn't want to spend much money...) I've been reading good things about switching one's parents to Ubuntu. Any thoughts out there?

VSTS Tester Demo Follow-ups

Last week, I delivered a VSTS 2008 Tester Edition demo to a prospective client. Following up on a few questions to which I didn’t know the answer: Q. Can I use Subversion with TFS? A. I get this question all the time from developers. It’s a perfectly valid question. The answer is no…but yes…sort of. The version control repository (and all data) must remain SQL Server. Yes, it’s proprietary. Further, if you plan to use TFS in your software development environment, but choose not to leverage it for version control, it severely limits the usefulness of the information elicited from TFS (because you’re not feeding in the crucial VC data). If you’re not leveraging VC in TFS, you’re probably not leveraging Team Build either. That said, while a fully-integrated TFS for ALM and SCM is the ideal, there’s a compelling argument to leverage TFS as a repository for requirements, scenarios, test cases, functional and load testing as well as defect tracking. TFS is an excellent repository to s...