Firefox 16 live: Here's What's New
mozilla.org
mozilla.org
The unfinished reading weighs me down every day, but I keep them open anyway. Some days I get productive and read a half dozen tabs, but never anything substantial. It's an embarrassing "problem."
Awesome / useless plugin idea: an artificial time bomb that removes the tab and all traces of the website from your history after being open longer than some period of time (e.g. one week). Obviously a bookmark circumvents this dilemma, but the problem itself isn't rational to begin with.
http://en.wikipedia.org/wiki/Firefox
It was a really long road but with 3.6 essentially gone and silent updates, developers can worry a lot less about legacy in the Firefox world.
Does anyone know if Firefox Mobile has matured to a point where it doesn't lag incredibly due to the huge memory footprint on Android?
Firebug will be getting faster as well as they are working on putting Firebug on top of the new debugging API in Firefox (which has much better performance than the old).
While my main profile is open most of the time, I can open webdev using "firefox -profileManager -no-remote" for some javascript debugging and close it when I am done without messing with my other open profiles. If I get bored I might fire up "wastetime" to browse some websites, or the "noextensions" profile to check a website with no extensions (sometimes noscript, better privacy, adblock plus, ghostery or even pentadactyl might mess up some website that I visit).
A really cool bonus is that with each profile I can save the opened tabs, so for example I have a "coursera" profile and it has all the tabs I need for the course I am taking (functional programming with scala). So, when I am studying I only need to open that profile either by itself or in addition to other profiles.
Just because Mozilla has their reason for making the change doesn't mean everyone has to be happy about the change. I'm not complaining about Firefox, I'm complaining about the number, and the corruption of what that number is supposed to mean.
I agree that it's a redefinition of what "version number" means: now it's essentially date based, rather than feature based (though the two are obviously correlated). But I can't see any obvious reason to read "redefinition" as "corruption". It's just different, and both Mozilla and Google had sensible reasons for making that change.
In fact, their decisions may make it worth questioning those assumptions more broadly. Is there a chance that your version numbering method is causing subtle problems for your own development process?
This rapid release schedule is just the most efficient way for these teams to deliver new features in a stable way. Taking 1-2 years to land code in the next major, stable version of the product just isn't practical anymore.
People get way too hung up on the actual number.
Don't be. There will be no "major additions" anymore. They will now release small features, quickly. So no major feature bump. Hence no need to wait for one either. It's like a number of small steps instead of one giant leap.
The point is that Firefox never wants to ever have a "major release" again. Small frequent changes work much better for everybody. So what are their options? Keep incrementing the minor number? The major major number then becomes meaningless and you end up with absurdities like "2.6.39".
I think the solution they chose is much better than the one Linus chose. What's the difference between 2.6.39 and 3.0? About the same as 2.6.38 to 2.6.39, and 3.0 to 3.1. Eventually they'll get up to 3.BIG and he'll call it 4.0 for no particularly reason.
Would you also be one to complain about the Linux kernel versioning scheme? It conveys exactly as much information as Firefox' does and works on the same principle. They just happen to have that extra first "major" number there, but it exists only for compatibility reasons. The change from 2.6.39 to 3.0 was exactly as "major" as pretty much every "point" release since 2.6.0. Yet I don't see people complaining about the version numbers every time a new kernel version is released.
Firefox still needs to improve its memory usage.
If Firefox users needed (or wanted) marketplace for (web) apps (or any other Chrome feature) they'd already be using Chrome ...
This way we'll be begging jQuery for Web Apps or some other abstraction layer that will do all the dirty work of cross browser compatibility...
I don't see a standard for Web Apps on http://www1.webplatform.org/ anywhere ...
Generally speaking, though, the difference between one definition of "web app" and another is very small, in terms of what the platform has to support.
I'll also note the perspective that sometimes it takes a couple of implementations before the "right" solution is known. Many evolutions of the web standards have followed varying implementations being played with in the field.
Now, why the "fuck" do you care if what I write here has anything to do with the article or not? Perhaps something is lurking behind the shadow you may want to look after?
In any case, given that my comment is being treated like any other noise, here's a few words to make it distinguishable...for whatever it is worth and for whoever that cares.
1. Whatever the heck is happening with Tags in bookmarks? Is anyone working on adopting any standards? People don't realize but holding up your bookmarks in FF via Tags is a death trap. Chrome apparently is not willing to support the tags and you will be stuck with FF if you care deeply about Tagging your bookmarks. Besides, FF for long has stopped innovating (read developing) their Bookmarks Manager.
2. Speed: No matter what anyone says and no matter the reasons, Chrome is certainly speedier. Besides, in my example (I use only two add-on and limited number of tabs) my hard drive spins and makes noise whenever I am on FF and it is absolutely silent when I am on Chrome (please don't blame my profile for it, I use multiple profiles and I know how to clean etc).
3. Syncing on Chrome is as straightforward as it should be and they also encrypt data.
Just a few on top of my list.
Firefox Sync is also straightforward (and syncs with Firefox for Android as well) and is also encrypted.
Unfortunately, didn't really get any momentum (mainly because there's just a long pipeline of things that are higher priorities), but maybe it'll go somewhere in the future. I agree that it's a weak point.
For the simple reason that noise drowns out signal, and because every damn article mentioning Firefox brings out someone saying the same thing.
If you had in some way brought it around to this particular release, your comment would have been on topic. Maybe there's a particular feature you've finally given up waiting for. Maybe some recent change in the UI that you dislike. Whatever! Don't just post empty blather, though.
("Fuck" here is simply used as emphasis, to indicate that I am exasperated by the prevalence of such empty comments.)
Agree, but people making such comments are also real and they may be as exasperated as you are.