Browser hopping: Twitch is a series of nine minigames created by Casey Reas to show off the capabilities of the Chrome browser. Each game calls for the user to maneuver a ball from one side of the window to the other. When the user succeeds, a new window opens, and the ball leaps seamlessly over to the next puzzle. Reas says that the game relies on Chrome’s ability to treat each window separately. Otherwise, he says, the nine windows required would compete for processing power and slow down the browser.
Casey Reas
Multimedia
But some say that new functionality will need to be standardized.
Google designed its Chrome browser to blur the line between online and desktop software. Now, the day after it released the latest beta version of the browser, the company has also launched a project designed to demonstrate Chrome's future potential. Called Chrome Experiments, the project showcases applications that demand strenuous data processing through multiple Web pages at once. Many of the demos would cause other browsers to crash, say the developers behind the experiments.
However, while some developers say that the techniques demonstrated through the project highlight new opportunities for building complex Web software, others worry that it may prove difficult to standardize the required features. They say that browser security remains a much higher priority.
One of the Chrome "experiments" is Twitch, designed by Casey Reas, a Los Angeles designer who is also an associate professor of design and media arts at the University of California, Los Angeles. Twitch provides a user with a tiny browser window containing a ball that has to be maneuvered from one side of the page to a target at the other. Once the target is reached, a new window appears, and the ball appears there along with a new set of obstacles.
Twitch takes advantage of Chrome's ability to launch each window or tab as a separate process on a computer--a feature that lets multiple windows run as if they were separate applications. Without that feature, Reas says, Twitch starts to slow down as the user progresses through the game. As more windows open, each minigame would compete for power from the computer's processor, and the game would chug to a halt.
Programmer and artist Josh Nimoy created another experiment, called BallDroppings. A user is presented with a single white ball dropping through a black screen, and he or she can draw lines to keep the ball from falling. When the ball bounces against each line, it chimes a note; as more balls drop, the user can keep adding lines, eventually creating a crowded scene for both eye and ear.
All of the experiments show how much a supercharged browser can do with JavaScript and HTML, which are the basic building blocks of Web pages, says Darrin Fisher, one of the engineering leads for Google Chrome. "People typically think that they have to use Flash to get things done," says Fisher. However, he says, the drawback is that not all browser functions will work with Flash.
Can laptops that do little more than access the Web compete with traditional computers?
Rockmelt is beautifully designed, but a review shows that it could get squeezed by Facebook and Google.
The company unveils the technical details of its operating system.
the link to the experiments is not working :(
I think the biggest hurdle will be to make it compatible for web designers making pages for IE and firefox. because right now chrome has a 1%, at best, share of the market. so it's really hard to justify testing in chrome.
Manufacturing in the United States is in trouble. That's bad news not just for the country's economy but for the future of innovation.
On Twitter
Become a Fan on Facebook
Subscribe to the Feed
JoelPM
1 Comment
Subtitle Not Accurate
I think the sub-title of this article is misleading. The second paragraph references concerns that others have about standardizing "the required features," but it doesn't enumerate what those features are. The only two the article seems to reference are (1) the canvas tag and (2) using a process-per-tab. The first is a proposed feature of HTML 5 and Chrome is simply supporting it. The second is an implementation detail that doesn't belong in a standard, and it actually helps address the issue of security by introducing boundaries between pages (specifically, the memory that the underlying page process has access to).
Mr. Crockford's comments are valid, though they would be more at home in an article commenting on the HTML 5 standard.
If there are features Chrome is introducing that aren't a part of the HTML 5 standard they deserve to be brought to light, but unfortunately I didn't notice any in this article.
Reply