Hasta La Gadget!

It goes without saying that any decent modern day office would come with at least one computer, whether it is for administrative purposes or simply as a productivity tool. Having said that, what kind of browser do you run in your enterprise environment? Assuming you have heard so much about Chrome from Google and have been raring to give it a chance, how about now, considering how additional improvements for Chrome at the office have been introduced recently.

The browser, after all, is a program that will see action most of the day, where it is used to access useful information, remain connected with people, and even to run web apps, regardless of whether you are at home, at work, or on the move. Chrome for Business might be the ideal candidate at the office, where it offers the flexibility for your IT administrator to configure Chrome so that it can automatically launch an alternate browser whenever you are running a web app built for older browsers. Should you want to use Chrome at work but fall back on older apps, it is painless ot switch seamlessly between the two browsers. That ought to provide you with enough peace of mind, no?

By Ubergizmo. Related articles: Intel mSATA 525 Series Review, Cooler Master Unveils Quickfire Stealth Mechanical Keyboard,

After four months in the alpha incubator, BitTorrent has released its Surf file-sharing plugin in beta not just for Chrome, its initial browser, but for Firefox as well. In an effort to make downloading and discovery easier, the new plugin has a status window for monitoring file progress plus a recommendation engine that’ll offer suggestions based on search terms. BitTorrent claims the results “prioritize legitimate content” and will “help creators and fans connect.” With ventures like SoShare, Sync and live-streaming in the works, this is yet another sign that a brand (arguably) once synonymous with illicit activities is at least trying to go legit.

Filed under: Internet

Comments

Source: BitTorrent (1), (2)

Gary Kovacs, (current) CEO of Mozilla, just took the stage here at D:Dive Into Mobile 2013 in New York City. It’s apt to be his last major stage appearance before stepping aside in order to “go back to his roots,” as described here, and hosts Ina Fried and Walt Mossberg were on hand to grill him on ongoing developments before he heads for other pastures. To start, Walt asked why the browser needed to be the operating system on a phone. Kovacs’ reply?

“The browser doesn’t need to be the operating system; it needs to incorporate the web. Such that discovery is easy, such that multiple stores can be accessed from the device — so we aren’t locked in, or generally encouraged to be locked within a single ecosystem.”

Filed under: Cellphones, Internet, Mobile

Comments

Now that Chromium has pledged its allegiance to Google’s new Blink rendering engine, Webkit is set to have the now-unnecessary Chrome-specific code stripped from it. Apple Webkit developer Geoffrey Garen kicked off a conversation on the project’s mailing list about removing the Mountain View-centric cruft, saying that it would streamline things and hopefully “make development easier and more coherent for everyone.” Garen adds that Googlers Adam Barth and Eric Seidel have already offered to pitch in with the clean up, but he asks that devs who will continue using the engine tidy things up as well. Over the next few weeks, code in Webkit related to the search giant’s browser, such as the V8 JavaScript engine, will be put up on the chopping block. With a Blink-infused Chrome slated to arrive in roughly 10 weeks, these changes shouldn’t mean much for the average web surfer, save for Webkit being a bit trimmer under the hood.

Filed under: Misc, Internet, Software, Apple, Google

Comments

Via: Slashdot

Source: Webkit Developer Mailing List

Earlier this week we talked about Google’s decision to move Chrome away from WebKit and develop its own Blink browser rendering engine in an effort to speed things up. At the time Chrome developers argued that WebKit had become difficult to deal with and developers often accidentally broke things while working on a project. Google says that Blink will give developers more assurance that when they change something, it will only affect what they expect it to affect.

Basically, Google says that it’s too easy to accidentally break things with WebKit and its Blink rendering engine will isolate the developer from the inner workings of content. The developers over at WebKit apparently didn’t appreciate Google’s take on their platform and are currently discussing how they could remove Chrome-specific code from the project. Removal of code that wasn’t Chrome-specific is one of the other reasons Google cited for leaving WebKit.

According to Google, there are about 4.5 million lines of code in WebKit that are there for other browsers that Chrome doesn’t use and Google wants to eliminate that code. Apple’s Geoffrey Garen, stated on the WebKit development mailing list, a suggestion to remove Chrome-specific code in an effort to make development easier and more coherent.

Code that developers at WebKit plan to axe includes code that specifically designed to integrate with the Google V8 JavaScript engine, any code having to do with the Google Skia graphics library, and support for the Google-URL library. Code having to do with page rendering and layout tests specifically for Chrome are also expected to be removed. However, Google Chrome isn’t the only browser that uses some of this code. Reports indicate that BlackBerry also uses Skia and Samsung uses V8 so removal of that code could affect those devices as well.

[via The Register]

WebKit devs ponder how to remove Chrome-specific code is written by Shane McGlaun & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.