Google Chrome 6 Expectations and Chromium 7 Outline

    Want an ultrafast browser? So do I. Want a web application and full HTML5 implementation? So do I. But you have to wait. And in some aspects, and wait a long time, because the work is titanic.

    Usually in software development, the time comes when programmers should distract their attention from adding cool new technology to ensure that all available functionality is fully operational. This moment, called code freezing, came in the sixth "milestone" of Google Chrome.

    Google believes in the constant updating of its browser and oppresses its line, demonstrating active work, both in development and in advertising. Chrome managed to smartly break into the top three dominant browsers, competing (not yet very serious) with Internet Explorer and Mozilla Firefox, as well as briskly surpassing Opera Software ASA and Apple browsers in the number of users. And this is just two incomplete years of the browser. (According to various sources, Google Chrome occupies from 7 to 9 percent of the global market ).

    It happens that, having missed the subway train, you will not wait long for the next, but you still have to wait until the arrival of the new train. This is what happened with some features of Google Chrome. They simply did not have time for a train called Chrome 6 and remain waiting for Chrome 7.

    Printing support was one of the relatively weaknesses of the Google Chrome browser compared to other browsers that had been on the web browser market longer, but Google worked hard to catch up and outperform its competitors. Failures also occurred in the form of poor implementation of printing the selected text fragment, and there were successes, such as unsuccessful attempts to crack the browser at Pwn2Own contests.

    As for printing issues, there is consolation for Windows users. The developers fixed a bug , and the change will be included in the release of Chrome 6, but Mac and Linux users will have to wait7 versions, when the entire print function will be redone. Long requests for the print preview function had an effect on the developers, and the function will be implemented, which is very joyful. Given the rate of release of new versions, this will happen relatively soon. Fall-winter 2010.

    Why Chrome 6?
    So why did Google decide to “upgrade” the version of Chrome? Are there really no new chips and opportunities, but only the “remaining to wait for a new train” function? Of course there is, but for the sake of which to fence a garden from a mass of versions? So, unlike version 5, Chrome 6 will:
    * Sync extensions. Now you don’t have to painfully delve into the vast, poorly structured official directory of extensions in search of your favorite add-ons. Loaded a browser and started synchronization. Wow!
    * Speed ​​up the output of images in SVG format .
    * Combine browser settings buttons and work with the page . Fashion trend lately. Both Opera 10 and Mozilla Firefox 4 practice a “one-button” model. Is it convenient? Decide to everyone.
    * Sync your browsing history . I think it’s a useful feature, although some browser users dream of a password synchronization function.
    * Optimize scalinghigh-quality images of high resolution. Users of multi-core processors will notice this especially well.
    * Well, of course, the standard performance increase of the V8 JavaScript engine, improved compatibility with web standards and promising developments like HTML5. In order not to be unfounded, I’ll apply the proofs:
    1. HTML5 support
    Google Chrome 5.0.375.99 Stable :

    Chromium 6.0.474.0 :

    2. Optimization of the JavaScript engine V8 MS Windows 7 Home, Intel Core 2 Duo P8400 2.26 GHz, 2 Gb RAM , Cache L2 3 Mb.
    Google Chrome 5.0.375.99 Stable :

    Chromium 6.0.474.0 :
    Progress is evident. Of course, a lot will be corrected and supplemented to the transition of the browser to the Stable branch, but this is the trend.
    * A lot of money for the vulnerabilities found. $ 3133.7 will not hurt anyone.

    In general, a sufficient set to assign a new digit to the version number.

    What else do not see in Chrome 6?
    * The function of moving the tab bar from top to side did not have time to “finish”. You can run a feature on Windows with the --enable-vertical-tabs option, but developers warn that this feature is in active development, and therefore may be unstable.
    * Support for full-screen video playback in HTML5. While Google Chrome does not know how to do this, it is very committed to the full-fledged work of HTML5 video, because Google clearly does not have the desire to depend on third-party plug-ins (for example, Adobe Flash).
    * Implementation of NativeClient for faster web applications. Of course, to say that this is done exclusively for the browser is premature, because, as you know, Google is working intensively on the Chromium OS operating system, but I would like to have a browser-OS hybrid (with a roll towards the browser).
    * A number of rather interesting features
    Delicious features, is not it?

    Given the long lull in the stable and beta branches of Google Chrome updates, builds of version 6 will soon fall into these channels. In the meantime, there are only dev-releases of Google Chrome 6. The browser war is in full swing.

    Sources :
    Chrome 6 Features
    Google Chrome Dev Releases
    Google Chromium Blog

    Also popular now: