Re:Chrome Release Cycle
by celticjames on Monday January 10, 2011 @04:30PM
(#2089817)
One thing that helps Chrome release often is that the api for building extensions is all javascript. By comparison, Firefox extensions can have binary components. This means there needs to be a certain amount of platform stability or extensions will break every six weeks. I think that in the future we'll see faster release cycles for Firefox as the api for extension building becomes more js based and less dependent on xpcom components.
[ Parent
| on HN ]
Re:Chrome Release Cycle
by lawfulfalafel on Monday January 10, 2011 @05:21PM
(#2089983)
I don't know about that. I would love to have an extension that made the omnibar a lot more like firefox's awesomebar (good indexing, can search for key phrases for title of article and the such) but to my knowledge that's pretty much impossible because of the javascript limitation (I hope I'm wrong here, not really sure).
I just wish google was a bit more subtle about wishing people search on google again when looking for previously viewed sites.
Funny, I wish Firefox's awesome bar let me press enter to go to the first result without pressing down first.
Re:Chrome Release Cycle
by cookiecaper on Monday January 10, 2011 @08:20PM
(#2090459)
Almost every extension I've tried has worked fine on Firefox 4, and certainly between the 3.x releases. While you might be right that this should be considered occasionally, it doesn't seem to be a big deal.
Re:Chrome Release Cycle
by IgorPartola on Tuesday January 11, 2011 @11:04PM
(#2094886)
Firebug, HTTP Live Headers, AdBlock Plus and a slew of other extensions I typically use do not work until a late beta is out.
Chrome extensions can have binary componants with NPAPI : http://code.google.com/chrome/extensions/npapi.html