Language Selection

English French German Italian Portuguese Spanish

Is Google on Crack?

Filed under
Google

This week I was supposed to explain why U.S. broadband prices are so much higher and U.S. broadband speeds are so much lower than in most other developed countries, but then Google made an unexpected reckless move in the wireless bandwidth market and here I am trying to explain it. We'll get back to broadband prices shortly, but for now let's turn to Google, whose stock may very well have already peaked.

What has me all worked up is Google's announcement this week that it intends to bid at least $4.6 billion in the Federal Communication Commission's auction of bandwidth in the 700-MHz band being reclaimed in 2009 from analog television. The auction price can and probably will go a lot higher than that, but $4.6 billion is the reserve price, so Google is saying it will unilaterally make sure the auction is successful and the spectrum is reallocated... IF certain conditions are met.

Google "requested that the Commission should extend to all CMRS-type spectrum licensees clearly delineated, explicitly enforceable, and unwavering obligations to provide (1) open applications, (2) open devices, (3) open wholesale services, and (4) open network access." For those of us who don't regularly hang with the FCC these proposed conditions mean: 1) users should be able to download software from anywhere and use it on their communication devices without restriction; 2) users should be able to use any communication device that meets the technical requirements for connecting to the network no matter who made the device; 3) third-party resellers should be able to buy wholesale bandwidth from auction winners, and; 4) other networks should be able to connect to the 700-MHz network.

Frankly, I see Google heading for a big loss on this one.




More in Tux Machines

NHS open-source Spine 2 platform to go live next week

Last year, the NHS said open source would be a key feature of the new approach to healthcare IT. It hopes embracing open source will both cut the upfront costs of implementing new IT systems and take advantage of using the best brains from different areas of healthcare to develop collaborative solutions. Meyer said the Spine switchover team has “picked up the gauntlet around open-source software”. The HSCIC and BJSS have collaborated to build the core services of Spine 2, such as electronic prescriptions and care records, “in a series of iterative developments”. Read more

What the Linux Foundation Does for Linux

Jim Zemlin, the executive director of the Linux Foundation, talks about Linux a lot. During his keynote at the LinuxCon USA event here, Zemlin noted that it's often difficult for him to come up with new material for talking about the state of Linux at this point. Every year at LinuxCon, Zemlin delivers his State of Linux address, but this time he took a different approach. Zemlin detailed what he actually does and how the Linux Foundation works to advance the state of Linux. Fundamentally it's all about enabling the open source collaboration model for software development. "We are seeing a shift now where the majority of code in any product or service is going to be open source," Zemlin said. Zemlin added that open source is the new Pareto Principle for software development, where 80 percent of software code is open source. The nature of collaborative development itself has changed in recent years. For years the software collaboration was achieved mostly through standards organizations. Read more

Arch-based Linux distro KaOS 2014.08 is here with KDE 4.14.0

The Linux desktop community has reached a sad state. Ubuntu 14.04 was a disappointing release and Fedora is taking way too long between releases. Hell, OpenSUSE is an overall disaster. It is hard to recommend any Linux-based operating system beyond Mint. Even the popular KDE plasma environment and its associated programs are in a transition phase, moving from 4.x to 5.x. As exciting as KDE 5 may be, it is still not ready for prime-time; it is recommended to stay with 4 for now. Read more

diff -u: What's New in Kernel Development

One problem with Linux has been its implementation of system calls. As Andy Lutomirski pointed out recently, it's very messy. Even identifying which system calls were implemented for which architectures, he said, was very difficult, as was identifying the mapping between a call's name and its number, and mapping between call argument registers and system call arguments. Some user programs like strace and glibc needed to know this sort of information, but their way of gathering it together—although well accomplished—was very messy too. Read more