stories filed under: "browsers"
by Mike Masnick
Wed, Sep 16th 2009 9:59am
I still can't figure out the reasons why content owners allowed Hulu to offer up TV shows in a browser... but then absolutely flipped out when they realized that the very same content can be seen on browsers on other devices as well. In the past, we've noted that Hulu was pressured to block the Boxee browser (which lets you view content on your TV) and the PS3's browser (also for TVs). Now, via hamill8152, we learn that Hulu is also blocking content on Skyfire, a mobile browser for Windows Mobile phones. The reasoning is the same as always (and, at the very least, kudos to Hulu for being upfront about the idiotic pressure it comes under from clueless content owners). Hulu explains the whole "windowing" thought process of the folks in Hollywood, and suggests that these windows will eventually go away. Of course, it's worth pointing out that Hollywood so disagrees with this that the MPAA has been pushing for ways to add more windows. Either way, the whole thing is silly. If you're putting your content on the internet, you're putting it on the internet. Pretending that televisions or mobile phones can't also view content on the internet makes no sense. One day, people in charge will understand this. Until then...
by Timothy Lee
Tue, Nov 13th 2007 3:26pm
from the open-source-browser dept
Google's GPhone (non-)announcement wasn't a big surprise, but some of the tidbits that are now emerging about the Android mobile OS are intriguing. For example, in a new video, Google's Steve Horowitz mentions that the default Android web browser will be based on Webkit, which he says is "the industry standard these days." Webkit is the open source package of web browser libraries that's at the heart of Apple's Safari web browser, and was originally based on the Linux Konquerer browser. Nokia gave the libraries a big boost last year when it announced a WebKit-based browser for its own mobile phones. And this year, Apple used WebKit as the foundation for the iPhone's web browser. The Google announcement further consolidates WebKit's status as a leading platform for mobile web browsers. The choice of WebKit for mobile browsing makes sense. Mobile browsers need to be fast and have a small footprint, and Apple originally chose the Konquerer codebase because it found it to be much leaner than Mozilla's codebase. The growing popularity of WebKit is good news for Mac Safari users (like me), who are less likely to see those annoying "your browser is not supported" messages when they visit websites. It's also good for the broader web-browsing public, as it represents the rise of a third major competitor in the browser market. As WebKit continues to grow in popularity, it will make more sense for website developers to focus on conforming to standards rather than customizing a site to the quirks of a particular browser. That, in turn, will force Microsoft (and Mozilla, but mostly Microsoft) to focus on conforming to the standards themselves, contributing to a virtuous circle of standards compliance that ultimately makes everyone's lives easier.