Does this give Firefox a little breathing room from the coming Chrome onslaught? I've heard developing AddOns for Firefox is a real pain and that AddOns for Chrome are easy in comparison. That, plus Chrome's speed is supposed to really start eating into Firefox's user share.
i've only written extensions for FF. i love it!!! it was a bit overwhelming at first. i was still learning javascript, too. now i feel like a master. i'm an "abstraction/high level" kind of programmer (er, computer scientist)---you can tell because my biggest pride is that my code is organized very well, and adding features is a joy. by this i mean that understand extension-land and writing extensions isn't all that difficult or nittygritty. i look forward to writing extensions for chrome, of course, though the power of ff extensions is pretty d* satisfying.
i believe chrome and jetpack are quite the same in their simplicity. google even said that in the future they hope to make chrome and jetpack esxtensions compatible.
regarding chrome's speed , firefox is starting to implement the multi-process browser ideas from chrome(a tab per process,a tab per extension) , with some of it is even in firefox 3.7 nightly build , which i feel is faster.
Yeah on all counts IMHO. I'm currently developing both firefox and chrome extensions and there is an order of magnitude difference in effort and technical complexity between them.
Jetpack is a great start for extension developers and it gives the FF team the ability to implement multiprocess browsing without breaking extensions left and right. As it stands now, FF is basically one big single threaded JS process (with other non scripting stuff delegated to other threads as possible). Small caveat: I am reasonably sure I understand how it works under the hood having worked so closely to it while writing extensions but I may have details wrong.
I'm a Chrome fan and full time user, but I think Firefox will reign king over the modern browsers for a while. They need to break the single threaded JS loop, finish up the out of process plugin work and continue work on reducing the overall memory footprint of long-running Firefox sessions from buggy extensions and the complexity of working with long lived , fragmented heaps. Jetpack itself will help contribute to some of this.
Firefox is still architected in places for machines of Y2K while Chrome had the advantage of assuming modern machines.
I wouldn't count the Firefox team out at any rate. They make a lot of progress on platform and footprint every release.
welcome to
╭══════════════╮
w w w . wowowbiz . c o m
╰══════════════╯
The website wholesale for many kinds of fashion shoes,
like the nike,jordan,prada,adidas, also including the
eans,shirts,bags,hat and the decorations. All the
products are free shipping, and the the price is
competitive, and also can accept online payment.,after the
payment, can ship within short time.
our price:
jordan air max oakland raiders $34--39;
Ed Hardy AF JUICY POLO Bikini $25;
Christan Audigier BIKINI JACKET $25;
gstar coogi evisu true jeans $35;
coach chanel gucci LV handbags $36;
coogi DG edhardy gucci t-shirts $18;
CA edhardy vests.paul smith shoes $32;
jordan dunk af1 max gucci shoes $37;
EDhardy gucci ny New Era cap $16;
coach okely Adidas CHANEL DG Sunglass $18;
thank you for your visit I wish you a happy new year ahead of schedule
∩∏∩
10 comments
[ 3.0 ms ] story [ 30.1 ms ] threadregarding chrome's speed , firefox is starting to implement the multi-process browser ideas from chrome(a tab per process,a tab per extension) , with some of it is even in firefox 3.7 nightly build , which i feel is faster.
Jetpack is a great start for extension developers and it gives the FF team the ability to implement multiprocess browsing without breaking extensions left and right. As it stands now, FF is basically one big single threaded JS process (with other non scripting stuff delegated to other threads as possible). Small caveat: I am reasonably sure I understand how it works under the hood having worked so closely to it while writing extensions but I may have details wrong.
I'm a Chrome fan and full time user, but I think Firefox will reign king over the modern browsers for a while. They need to break the single threaded JS loop, finish up the out of process plugin work and continue work on reducing the overall memory footprint of long-running Firefox sessions from buggy extensions and the complexity of working with long lived , fragmented heaps. Jetpack itself will help contribute to some of this.
Firefox is still architected in places for machines of Y2K while Chrome had the advantage of assuming modern machines.
I wouldn't count the Firefox team out at any rate. They make a lot of progress on platform and footprint every release.
- Chrome extensions are beating jetpacks by a long shot.
- There should be a unified/standard way to build extensions for browsers based on javascript.