Jetpack has been around since May 20, 2009 https://addons.mozilla.org/en-US/firefox/addon/12025/version...
What's new in Firefox 4 is that it is integrated instead of being an extension.
I didn't say "introduction" of Jetpack.
Greasemonkey is a third-party extension. It wasn't created and isn't maintained by Mozilla, so it can't be officially obsoleted by Jetpack.
That said, if Jetpack supported transparently installing Greasemonkey scripts (the way Chrome does -- http://mashable.com/2010/02/01/google-chrome-greasemonkey-2/), it would effectively obsolete Greasemonkey because there'd be no need to install it.
Until then, there are 40k user scripts on userscripts.org that still need Greasemonkey installed in order to work: http://userscripts.org/.
"Obsolete" may be an overloaded term, but this is the plain English usage, and it's the usage I'm using.
EDIT: I misunderstood that Jetpack was originally an extension and not just a codename for a new feature.
Oh you want to change X? Click show menu bar on the orange thing! Notice the menu? Notice that your orange bar disappeared? Wonder how to get it back? It's in view, uncheck menu bar!
So NOT intuitive.
Also, their feedback thing was down when I tried to report this :(
On top of the address bar isn't the point. It's a nice touch that emphasizes the metaphor for "real" tabs, like on a paper folder, but it doesn't have the huge usability bonus of Chrome's implementation.
The important thing is that in Chrome, the tabs are on the very top pixel of the screen (in Windows or a Linux UI with no top bar). Since I browse with a hand on the mouse, this means that I can switch between tabs by chucking the pointer at the top of the screen and scrubbing left and right, instead of having to pay attention to vertical alignment.
I realize that this feature has been in tiling window managers for quite some time, it's just nice to have it in Windows now.
IMHO, there's a little too much "free space" on the top of Chrome's tabs, and Safari got it just right.
I guess they are going to hide it before FF4 comes out of beta. You can force quit the bottom firefox and the misbehaving flash object will die: http://grab.by/5iXj
They also need to adopt something like Safari's URL-field-as-progress-indicator, or at least an animating graphic to indicate loading. Simply switching the refresh button to an 'X' is way too subtle, and at first I didn't think it was actually loading anything.
Edit: Oh, that's weird. I fired it up again and saw the stopwatch graphic and other loading indicators. Now I'm wondering if these didn't work the first time around, or if I just wasn't paying attention to them given that I'm habituated to Safari's indicators.
"OSX and Linux Themes: The new interface described above will soon be available for Mac and Linux users."
1 Password, Delicious Bookmarks, Firebug, Greasemonkey, Google Toolbar, Stylish, YSlow and others...
But just give it a little time, firefox 4 is definitly worth the wait.
Seems faster to start, although it's disabled every addon I had before, so hardly a fair test.
In general it seems to be more like Chrome. Which I think is probably a good thing - if Chrome has demonstrated a better way to do things, I don't have a problem with Firefox following their lead.
Otherwise, it does feel faster, though I find it funny that Firebug currently doesn't work even though it's prominently listed as one of their main developer tools.
They worked really hard on making the add-on interface more intuitive and cleaner, but really the thing everyone wants is better memory management.
It really feels like Mozilla is playing catch up now, trying to take things back to basics & fix some core issues (like startup times, plugins slowing things down, JS performance & so on).
Kudos to Google for giving the browser that once we all used something to aspire to.
Sometimes the min/max/close buttons do not appear. Making me have to go to the "firefox" button and hit exit.
Why does the "firefox" button take up all that space? If they are going to copy Opera and add the "firefox" button, then copy Opera and make it look good. (talking about maximized window)
Moving the tabs is still really bad. Chrome and Opera both have really smooth transitions and opera even adds nice preview windows.
On the flip side
It feels much more responsive. I don't care about the actual numbers just the feel.
The new addon manager that they copied from chrome looks much better, then the previous and even chromes.
The loading circle on the tabs is really nice touch. Its nice being able to see how far along a tab is in its loading phase. This is a feature I see all browsers copying very soon.
Electrolysis (even more process seperation) merged with trunk recently: https://bugzilla.mozilla.org/show_bug.cgi?id=571166
Hardware accelerated graphics should be turned on by default soon as well.
And of course, the continued iteration of the new theme, many platform featured to be added...
It is almost solved with the memory fox plugin, but I still need to restart Firefox 3.x every month instead of every week.
I hope that Firefox 4.x will address this problem.
I'm genuinely curious why that is. Options I can think of are a) they are spotlighting features that take away a perceived edge that Chrome has, b) they really are playing feature-catch-up and letting other browsers determine the roadmap, or c) some features (the web console?) are far more ambitious than I've given them credit for.
Can anyone shed some light on what is really going on here?
The three highlighted features are 'new addons manager,' webm support, and fixing the :visited privacy issue. NONE of these are in any released Chrome, although the early early preview of Chrome 6 has WebM support.
Of the three UI elements highlighted, tabs on top is the only one in Chrome (or did I miss the Chrome button in some developer preview?).
Looking further down, I was thinking that WebSockets, Indexed DB, Crash Protection, and the key feature of JetPack (Add-Ons not requiring restart) were all pioneered by Chrome. That leaves The Web Console, which I have not yet tried so can't really comment on either way, and the two givens (HTML5 and CSS3). To my eyes this seemed odd. But I take it you disagree?
According to wikipedia, Chrome 5 does not support WebM: http://en.wikipedia.org/wiki/Chrome_%28browser%29
WebSockets: Yay, you're finally right, Chrome did pioneer WebSockets. Sadly, it did not update its implementation to reflect the changes to the standard based on feedback from the numerous other browser vendors that actually implemented it but chose not to release it because of it volatility.
IndexedDB: Google was actually pushing for Web SQL Database, which got rejected. Learn more here: http://hacks.mozilla.org/2010/06/beyond-html5-database-apis-...
Crash Protection: IE8 was the first browser with this feature.
Jetpack: Ok, this one is important right? So for bonus points, let's look at the first jetpack release:
https://addons.mozilla.org/en-US/firefox/addon/12025/version... (scroll the to bottom: May 20, 2009)
Now for Google's launch of their great extensions platform: http://techcrunch.com/2009/12/08/chrome-extensions-live/ (December 08, 2009). Darn, guess Google stole that one from Mozilla's playbook (and yet, still no powerful extensions :().
WebConsole: Everyone and their mom has been using Firebug since the dawn of time. Chrome wasn't even an inkling in Google's eye then.
HTML5: Firefox 4 is STILL the only browser to support HTML 5 parsing. Previous versions of course supported other features such as video and audio, but since you didn't go into details here, I'll leave it at that.
CSS3: No details again? Ok, well rounded corners has been in Firefox so long I can't even remember (1.5 or 2?). Lots of these features were around before Chrome existed. But no more for this since you only mentioned it in passing.
Call me a fool for taking the bait (http://xkcd.com/386/), but with all due respect please stop trolling, and learn about what you're talking about before you speak.
... which is slightly before the first Jetpack alpha which was May 20 2009.
In any case, the issues that both extension systems try to address have been well-known for some time. It isn't surprising that multiple people came up with similar ideas on how to fix them.
ninja edit: Got timelines mixed up first time 'round
> ... and learn about what you're talking about before you speak.
> Ok, if you want to know all the features ...
Now, back to the discussion.
WebM: You are correct, Chrome 5 does not support WebM, although it is in the dev version of Chrome 6. I do think, however, that the perception of the feature is it was Google's first, considering its their codec.
WebSockets: Please don't try to pretend Chrome is ignoring the standards changes. The new version is in Chrome 6 for you to try, if you're interested. My point is that this is a feature they drove to market, and got everyone else to support, hence my perception of it.
IndexedDB: Again, the specific technology is beside the point. Google has been pushing for offline storage since Gears, and now everyone else is implementing it (albeit a slightly different backend). You see where I'm going with this.
Crash Protection: I stand corrected. I always think of Chrome being the browser pushing the segregated processes, better plugin separation, etc, but it appears IE8 was first. Still, Firefox is definitely not leading the market on this one.
JetPack: as per aboodman, I will call this a wash.
WebConsole: It is a bit specious to give Firefox credit for a 3rd party extension (FireBug), but regardless, this feature doesn't support my point, and I never pretended it did.
HTML5/CSS3: Every browser coming out has been touting these two technologies for ages, most of the time without a clear consensus on what they even entailed. At this point you couldn't not put them on a feature list. So I don't particularly consider it valuable or surprising to see them.