Dev.SN ♥ developers
Sections
Dev.SN
from the non-soluble-fiber-is-good-for-digestion dept.
Fluffeh writes:
"Google has officially invited 34 cities in nine metro areas to become the next batch of the Google Fiber rollout.
Google said it 'genuinely would like to build in all of these cities,' but that the complexities of deploying networks may not allow it. 'During this process, we will work with each city to map out in detail what it would look like to build a new fiber-optic network there,' Google said. 'The most important part of this teamwork will be identifying what obstacles might pop up during network construction — and then working together to find the smoothest path around those obstacles. Some might be easy, some might take some creative thinking or a few months to iron out, and in some cases there might be such local complexities that we decide it's not the right time to build Google Fiber there.'"
(Score: 1) by akinliat on Thursday February 20 2014, @03:32PM
Except that both you and dmc are outliers. Most people who run servers aren't commercial software developers who make their source available via git (hey, wait a minute ...) or able to run a new hosting paradigm that can be done with only 768Kbit upstream (see dmc's post). It's people like me, or worse, who are the problem, because we're, well, common. There are a lot of folks like me. If you don't believe me, pop over to WebHosting Talk [webhostingtalk.com] sometime. It's as busy as the (sigh) pre-Beta /. And we'll suck down bandwidth like a two-dollar whore.
I'm not saying that I'm happy about Google's choice here (neither are some folks at Google), but I don't think it's either arbitrary or unreasonable. They've identified a potential problem (excessive bandwidth use by folks like me) and formulated a policy to deal with it. Is it the least restrictive policy possible? Well no ... but it's not crazy either.
Since dmc mentioned antitrust, there's also one other factor that may be playing into this -- I don't think Google really wants to start competing with the datacenter industry.
Just think, datacenter bandwidth currently runs anywhere from $1-$250/Mbit. The low end prices some of the bandwidth into the cabinet costs, and they also cut other corners. Google would be offering bandwidth at $0.07/Mbit (not counting the free service). Google already has a huge influence on web traffic, and with Android, they also have a strong presence at the network endpoint. Now they're providing network access to a whole 'nother set of endpoints. Getting a foothold on the content sources (servers) could be awfully sketchy from an antitrust viewpoint.
BTW, I think telecommuting would be allowed -- as long as you weren't running a server from your house.
(Score: 2) by dmc on Monday February 24 2014, @05:57PM
It's not crazy- it's calculated. Google wants as much control as possible. People who might be able to succeed comercially utilizing low bandwidth servers hosted at residences are a threat to Google's bottom $$ line. Sure, they may be outliers, but so were Page and Brin when they were starting out. Being able to make overly broad restrictions in the ferengi print, and then selectively enforce, or worse yet- cripple the ability of innovators to get investment capital for great ideas because of the murky legality of the ferengi print is cold-blooded calculation on their part. You are right, there is nothing crazy about it. Just criminal, since it satisfies the three criteria of a section 1 Sherman Antitrust violation.
The very, very simple honest solution is for GoogleFiber and other ISPs to stop the *fraudulent* advertising claims about bandwidth, and actually charge reasonably based on bandwidth used. (fixed costs, plus variable costs for the bandwidth). This always scared people because they thought "ooh, now my netflix usage will be more expensive". Hopefully the fallout of the demise of Net Neutrality and the extra money that Netflix is now paying to Comcast, and it's no doubt ultimate eventual being passed onto consumers will make people realize that that argument against reasonable data-usage charging was a bad argument.
I'm not looking to peg bandwidth 24/7. There is _a lot that can be done_ with low bandwidth, as long as you are free (in the Net Neutrality way that I argued and which US Navy Information Warfare Officer Dave Schroeder agreed with) to do so.