Chrome 27 Beta now available, promises faster speeds

Chrome 27 Beta browser has been released by Google, bringing with it some goodies for developers, as well as faster page loading to the tune of about 5-percent. Users who don’t mind dippingo into beta territory can grab the latest download now from the Chrome beta page. We’ve got a run down of the new features and improvements after the jump.

Chrome 27 Beta

The obvious feature most users will notice is the speed improvements, which are said to increase the rate of content loading by 5-percent. This is due to behind the scenes changes to the browser’s resource scheduler, decreasing pre-loaded resources and using an idle connection more often. In addition, webpagetest.org Speed Index values are now included in the metrics used to assess page load speed improvements.

Other changes and additions are specific to developers, and include HTML5 date and time forms, which are featured in the image above. There’s also now live audio input to Web Audio API for the Windows and Mac versions of Chrome, as well as Sync FileSystem API for Chrome Packaged Apps. Improvements have been rolled out for the network panel, bringing customizable columns and the ability to “Copy as cURL” a resource by right-clicking on it.

There are a variety of other features for devs, which those who are interested can check out in full here. In case you didn’t hear, Google announced yesterday that it will be forking a new rendering engine called Blink from WebKit, promising to bring with it speed and to eventually spur innovation. You can read more about those plans, as well as what one Chrome dev has to say, here.

[via Chromium]


Chrome 27 Beta now available, promises faster speeds is written by Brittany Hillen & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

Chrome 27 beta wrings out more speed, streamlines HTML5 input

Google Chrome logo

It’s like clockwork, really. Chrome 26 has barely hit the stable track, and Google is already posting a Chrome 27 beta for desktops and Android devices to show what’s next. Apparently, that future centers mostly on raw efficiency: Google has eked out an average 5 percent speed boost through a more aggressive resource scheduler. It also has a simpler interface for date and time forms on HTML5 pages. Most of the other upgrades coddle developers, such as the introduction of live audio input for the Web Audio API and an offline storage API for Chrome Web Store apps. There’s no mention of Blink, so those who were expecting rapid adoption of the web engine beyond Chromium will be disappointed — even so, it’s good enough that we could see internet Guinea pigs giving the release a try.

Filed under: , ,

Comments

Via: Chromium Blog

Source: Google Chrome Beta

Speed matters argues Chrome dev as Google under fragmentation fire

Google’s decision to branch off from WebKit and develop its own Blink browser rendering engine is a matter of speed not fragmentation and control, one Chrome team developer has argued, pointing out that what’s currently the de-facto standard has already become a weight around devs’ necks. “To make a better platform faster, you must be able to iterate faster” Google London’s Alex Russell argues, likening the sluggishness of adding and tweaking WebKit features to the inefficiency of using an old computer when newer, faster ones are available. As a bonus, he points out, developers will be less likely to inadvertently break something when modifying the Blink engine, a situation Russell says can often occur when dealing with WebKit.

chromium_blink_speed

“Blink gives developers much more assurance that when they change something, it’s only affecting the things they think it’s affecting” he explains, thanks to the engine’s Content API boundary. That’s the part of Blink which – though for the large part following the WebKit API design – differs in that it isolates Chrome developers “from inner workings of content.”

For Russell, though – and presumably Google as a whole, given its web/cloud-centric focus – the speed potential for jumping ship to Blink is what really makes the fragmentation worthwhile. The Chromium team has enjoyed such streamlining in Google’s own “Chromey” parts, he points out, and now will get the same in the underlying engine. That, the reasoning goes, means a browser that is improved faster and keeps better pace with the demands of users and developers.

“Directness of action matters, and when you’re swimming through build files for dozens of platforms you don’t work on, that’s a step away from directness. When you’re working to fix or prevent regressions you can’t test against, that’s a step away. When compiles and checkouts take too long, that’s a step away. When landing a patch in both WebKit and Chromium stretches into a multi-day dance of flags, stub implementations, and dep-rolls, that’s many steps away. And each step hurts by a more-than-constant factor” Alex Russell, Chrome team, Google

The losses from adopting Blink are the obvious ones, Russell says: divorcing development from “a community of hugely talented people” working on WebKit, for instance. Some old faces are likely to be present, however; Opera has confirmed, TNW reports, that it too will be using Blink having already committed to switching to Chromium back in February.

“When we announced the move away from Presto, we announced that we are going with the Chromium package, and the forking and name change have little practical influence on the Opera browsers” Opera spokesperson

Who will follow next remains to be seen, though given Google’s footprint in smartphones and tablets with Android, not to mention its push to move users onto the web in Chrome OS, developers certainly won’t be able to avoid Blink moving forward.


Speed matters argues Chrome dev as Google under fragmentation fire is written by Chris Davies & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

Chromium announces new open source rendering engine project Blink

WebKit makes the web go ’round, and yet it is soon to be joined by a new kid on the block: Blink, which was announced on Chromium’s blog earlier today. Says Chromium, the decision to create a new rendering engine “was not an easy” one, but ultimately good will come from it. Developers don’t need to worry, as the announcement reassures that little will change for them during the initial rounds of work.

Chromium

As pointed out by Chromium software engineer Adam Barth, Chromium utilizes a multi-process architecture that differs from that of other WebKit browsers, with the multi-architecture support leading to a slurry of ever-increasing complexity that serves as a sort of ball-and-chain on the ankle of innovation. Blink, which will be open source, aims to solve this issue and provide, by proxy, a boost in innovation.

Aside from that, optimistic attitudes tout the upcoming rendering engine as a possible boost to the “open web ecosystem” as a whole, although it is acknowledged that introducing a new rendering system has the potential to significantly impact the Internet, and developers could eventually have more work on the coding end of things.

According to Barth, the initial work will concentrate on getting rid of digital clutter, including the removal of about 7,000 files and 7 build systems, which will total in excess of 4.5 million lines of code. This will result in vast internal architectural improvements, but won’t bring much change to web developers. Guidelines have already been posted regarding interoperability, standards, and other such related items.

[via Chromium]


Chromium announces new open source rendering engine project Blink is written by Brittany Hillen & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

Chrome 26 for Android gets stable release with autofill and password syncing

Chrome 26 syncing

Perpetually forgetful Android users no longer have to adopt a Chrome beta to coordinate their lives. Just a month after the test version of Chrome 26 arrived with autofill and password syncing, its stable version has appeared with the same option to remember form and login details between supporting desktop and mobile Chrome builds. There’s no talk of the SPDY-based proxy, however: aside from tune-ups, the syncing is the main highlight. That’s still enough for us to justify swinging by Google Play for the update.

Filed under: , , ,

Comments

Via: Chrome Releases

Source: Google Play

Google forks WebKit with Blink, a new web engine for Chromium and Chrome (update)

Google forks WebKit with Blink, a new web engine for Chromium and Chrome (update)

You could call WebKit the glue that binds the modern web: the rendering engine powers Apple’s Safari, Google’s Chrome, and many mobile browsers past and present. Things are about to unstick a little. Google believes that Chromium’s multi-process approach has added too much complexity for both the browser and WebKit itself, so it’s creating a separate, simpler fork named Blink. Although the new engine will be much the same as WebKit at the start, it’s expected to differ over time as Google strips out unnecessary code and tweaks the underlying platform. We’d also expect it to spread, as the company has confirmed to us that both Chrome and Chrome OS will be using Blink in the future. We’re safely distant from the Bad Old Days of wildly incompatible web engines, but the shift may prove a mixed blessing — it could lead to more advancements on the web, but it also gives developers that much more code to support.

Update: The Next Web has confirmed that Opera, which recently ditched its Presto engine for Webkit, will indeed be using Blink as it’s already hitching its proverbial wagon to Chromium.

Filed under: , ,

Comments

Source: Chromium Blog

Mozilla and Samsung collaborating on new Servo web browser engine for Android and ARM

Mozilla and Samsung collaborating on new Servo web browser engine for Android and ARM

It’s a fairly bold claim, but Mozilla and Samsung have announced today that they’re now attempting to “rebuild the web browser from the ground up on modern hardware.” That initiative takes the form of Servo, a new web browser engine designed for Android and ARM and based on Mozilla’s Rust programming language, which itself sees a new release today. Expectedly, details on the browser engine remain light, with Mozilla and Samsung offering no indication of a release schedule or a final product. In the blog post announcing the engine, Mozilla says only that it’ll be “putting more resources into Servo” in the coming year as it also aims to complete the first major revision of Rust, and that it and Samsung will be “increasingly looking at opportunities on mobile platforms.” You can find the full announcement, and the source for both Rust and Servo if you’re so inclined, at the source link below.

Filed under: ,

Comments

Via: The Next Web

Source: Mozilla

Samsung and Mozilla working on new web browser engine for Android

Samsung and Mozilla announced today that they’re partnering up to build a “next generation” and an “advanced technology” web browser engine, which they’re calling Servo. Mozilla said in a blog post announcing the news that the two companies will build a new engine from the ground up, but “rethinking old assumptions along the way.”

mozilla-firefox

Essentially, Mozilla and Samsung want to bring this new web browser engine to Android devices running ARM, and in order to make a secure, yet fully open experience, Servo is written in Rust, which is a new programming language developed by Mozilla. You can actually download the code on Github and play around with it, but Mozilla notes that it’s in its very early stages.

Details are pretty scarce at this point in the development process, and we’re not quite sure yet what exactly this next-generation web browser engine will be capable of, but we’re guessing it’ll be pretty revolutionary if Mozilla and Samsung put their heart into it. Rust has been in development for a couple years now, actually, and they expect have the first major revision done sometime this year.

However, the partnership seems to be a perfect fit for the two companies. Mozilla is providing the Rust programming language, as well as Servo, while Samsung’s experience with ARM will no doubt be of tremendous help for Mozilla in bringing the technology to Android devices in the future.


Samsung and Mozilla working on new web browser engine for Android is written by Craig Lloyd & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

Firefox 20 improves private browsing and user experience

Mozilla has just updated its Firefox browser to provide users with several new features that they have been asking for. The new Firefox 20 improves private browsing, integrates your download window with your toolbar, brings getUserMedia to developers, and offers an overall better user experience. Firefox has also simultaneously updated its Firefox Browser for Android app with similar features.

Firefox 20 brings enhanced private browsering and user experience

Before the update, you would have to choose between regular browsing or private browsing with Firefox. You couldn’t have both. Now, Firefox has taken a page of out Google Chrome’s book and is now allowing you to simultaneously do both. This is great if you have multiple email accounts and do not feel like signing out of one just to access another. It’s also great for “other” things as well. This new feature is included in Firefox Browser for Android.

Also with this update, Firefox’s Download Manager is now integrated into your toolbar, so you can easily monitor your downloads without opening another window. You will be able to view and minimize your downloads with one simple click. And finally, Mozilla has integrated getUserMedia with its browsers, which allows developers to create web apps that can utilize the user’s camera and microphone. You can download the latest Firefox browser here.

Firefox Browser for Android now allows you to add shortcuts to your homescreen for your favorite sites, similar to Google Chrome’s Android app. Mozilla has also provided support for ARMv6 devices, so now many more lower-end Android phones will be able to take advantage of Firefox Browser for Android. Mozilla states that by supporting ARMv6 devices, it is able to bring its service to over 50 million more phones. In similar news, Mozilla is also gearing to launch its FireFox OS phones later on this year to over 18 operators. It’s an impressive OS looking to break into the mobile market.

[via Mozilla]


Firefox 20 improves private browsing and user experience is written by Brian Sin & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

Firefox G-Fox: Plush Edition (hands-on)

Image

With the introduction of Google’s Chrome and stepped-up games from the likes of Internet Explorer and Safari, Firefox is arguably not quite the darling of the browser wars it was when it first hit the scene in 2003. And while Mozilla has certainly made progress on that front, the organization understands that diversifying is an important factor in the future success of the company, first through Thunderbird and more recently through the Firefox OS, a mobile operating system targeted toward users in developing nations. G-Fox, meanwhile, marks a decidedly different direction for the foundation, which has made its name in the world of software. It’s an adorable attempt, perhaps, to take the world’s bedrooms and playrooms by storm.

The plush is the real-world port of G-Fox, Mozilla Online China’s large-headed, big-eyed take on the American mascot, Kit. The fox was first spotted in the wild at last year’s Mobile Asia Expo in Shanghai. Mozilla Online wasn’t talking it up too much at the event, but naturally, we couldn’t wait to get our hands on an early build. And for a first-generation product in a new space, we have to say, in the whole time we’ve been playing around with G-Fox, we’ve yet to encounter a single crash or slowdown in spite of extensive squeezing, head patting and tossing up in the air, adorably.

Comments