Showing posts with label Chrome. Show all posts
Showing posts with label Chrome. Show all posts

Tuesday, 26 July 2011

Boot To Gecko: Mozilla’s Open-Source, Mobile Answer To ChromeOS


Straight from the heart of Mozilla’s developer newsgroup comes news of an ambitious new project: a standalone, web-based operating system. If that concept sounds familiar, I’ve also just described the core of Google’s Chrome OS which we’re beginning to see pop up on netbooks. The big twist?

It’s currently being developed for mobile devices. And it’s partially Android-based.

According to Dr. Andreas Gal, researcher at Mozilla, the impetus behind the Boot to Gecko project is to “make open web technologies a better basis for future applications on mobile and desktop alike”. A lofty goal to be sure, as the core underpinnings would ultimately extend beyond just mobile devices. Should Gal and his colleagues (and really anyone who wants to help) succeed, Boot to Gecko would have the potential to change how we interact with the web, regardless of platform.

Gal breaks the process down into actionable steps. First, the Boot to Gecko project aims to take the primary functions of a mobile device (i.e. “Telephony, SMS, Camera, USB, Bluetooth, NFC”) and create web APIs to handle them. From there, they intend to develop a way for web pages and applications to safely access those components as needed. They hope that by doing this, they (and other intrepid developers) will be able to create native-grade apps that run directly on the web instead of only being available on certain devices.

As I’ve mentioned, the open-source project is based partially off of Android — nothing terribly high-level though, just the kernel and the drivers so as to ensure that whatever progress they make can actually boot. It also doesn’t hurt that Android works (and in many case, has been made to work) on plenty of different hardware configurations, which is exactly what they need to see if the concept pans out. As it stands, development is in such a nascent stage that we have no idea what to expect visually, so no images yet folks.

Personally speaking, this idea has me on the edge of my seat. It will take a lot of work, and a lot of time, and there’s no guarantee that we’ll ever see a complete release. That’s the funny part though: I don’t think it really matters. If all they ever did was finish the API for telephony and SMS messaging, that would still signal a tremendous shift in how we use the web. Boot to Gecko will inevitably draw comparisons to ChromeOS (and I was guilty of this just a few paragraphs ago), but we stand to gain a much richer online experience if B2G comes to be. Only time will tell if these gentlemen succeed, but we’ll be certain to keep you up to date during the ride.

Thank you :
http://techcrunch.com/2011/07/25/boot-to-gecko-mozillas-open-source-mobile-answer-to-chromeos/

Tuesday, 19 July 2011

Firefox world loses Web dev guru to Chrome


For years, an extension called Firebug has been a powerful tool that kept Web programmers loyal to Firefox.


But now, as browser makers add their own tools geared to attract those who build Web sites and applications, the lead Firebug programmer has taken a job with Chrome, CNET has learned.


"Monday, I start work on next-gen Web dev tools at Google on the Chrome browser team. Consequently I will no longer be contributing routinely to the development and maintenance of Firebug for Firefox," John J. Barton told members of a Firebug mailing list yesterday.


The change reflects the new rules of the browser market in which Firefox no longer holds such a central location.


Firebug was dominant in the days when Mozilla's Firefox was the dominant challenger of Microsoft's Internet Explorer, but now the browser market is as competitive as it's ever been. Chrome is steadily gaining usage share at Firefox's expense. On top of that, the use of mobile browsers is exploding, and the scope of what people do with a browser has expanded tremendously.


Web programming is a hot area as the era of static Web pages gives way to the era of dynamic Web applications with animated elements, interactive user interfaces, and heavy-duty software written in the JavaScript language. That makes the task of creating developer tools harder.

Barton had been an IBM employee. IBM made Firefox its default browser a year ago, a major endorsement for the open-source browser, but evidently IBM's priorities don't extend as far as Firefox these days.


"I think our current drive to re-architect Firebug is on the right track, but I could not obtain another year of support from IBM to contribute to that work," Barton said.


Web developer tools in browsers are under rapid development as browser makers court Web programmers. Chrome has its suite of developer tools. Apple's Safari has its Web Inspector and other tools. IE has the F12 developer tools. Firefox has a developer tools group, too.


Firebug is an elaborate extension for Firefox. But it's been a lot of work at times to keep Firebug updated as new versions of Firefox arrived. That was the case two years ago when Mozilla was trying to turn the new-version crank faster, and it's even more the case now that Firefox is fully engaged in Mozilla's new rapid-release program for Firefox.


Thus, Barton described Firebug's present challenges:

Working on Firebug with this great group of contributors was fun and I believe we had a tremendous impact on the Web over the years when Firebug was the only decent Web debugger

Now all of the browsers have (or will soon have) their own debuggers. Basing next gen work on Firebug is not practical. The pace of change in browsers is too fast for our team size. Firebug hasn't really been able to keep up with Firefox, let alone compete with other tools. Moreover, the shift from desktop to mobile and from one high-tech browser (Firefox) to three or more requires additional development effort."


Dion Almaer, who had worked on developer tools at Mozilla earlier in his career, noted the significance of Barton's new job in a blog post today.


"Firebug used to be the way you debugged your sites, but that is changed," Almaer said. "It is too early to claim that Firebug is zombied, but all eyes will be on that...especially as we see other browser tools continue to blossom."


Thank you : http://news.cnet.com/8301-30685_3-20080338-264/firefox-world-loses-web-dev-guru-to-chrome/#ixzz1SYhX9AHZ