Slashdot Mirror
Firefox 30 Available, Firebug 2.0 Released
Today Mozilla made Firefox 30 available, a relatively minor release after the massive redesign in version 29. According to the changelog, new features include VP9 video decoding, support for Opus in WebM, and horizontal volume control for HTML5 video and audio. Developers got support for multi-line flexboxes and hang reporting for background threads. There were also a number of security fixes. The Android version of Firefox received better support for native text selection, cutting, and copying, as well as predictive lookup for Awesomebar entries. The availability of Firefox 30 coincides with the launch of Firebug 2.0, which features an updated UI and a new debugging engine called JSD2. Significant new features include JavaScript syntax highlighting and de-minifying, improved code auto-complete, and the capability to hide or show individual Firebug panels.
...with this rapid release schedule. Firefox is trying to update more often than Java nowadays.
Run an unstable branch like everyone else, and run a testing/beta branch to become the next stable. It will make life a lot easier.
Do not look into laser with remaining eye.
If yes then I'm still not using it. Palemoon all the way.
Only the State obtains its revenue by coercion. - Murray Rothbard
Does it still require Classic Theme Restorer?
[Fuck Beta]
o0t!
The linked changelog and description are for Firefox 28. For FF 30: http://www.mozilla.org/en-US/firefox/30.0/releasenotes/. Even accounting for FF's release schedule and for Slashdot delay, that's a bit much. Only important change for me as an end-user looks to be:
Ignore autocomplete="off" when offering to save passwords via the password manager (see 956906)
I'm having flashbacks to the movie Airplane!...
Now arriving at version 29, version 29, version 30...
Do not look into laser with remaining eye.
I hope they fixed the memory usage problem I've been having since the last update. Lately for me FF has been running up over 3GB of memory usage and then crashing after anywhere from 6 to 12 hours with only 7 or 8 tabs open. It's been driving me crazy.
...if they used sane version numbers?
Probably something like 12.0.1...
Do not look into laser with remaining eye.
Yes
They have a brand new sync as of 28. I don't like it because the new sync protocol theoretically lets them get access to your sync'd data. They promise not to, but I wish they'd just make it easy to host your own personal sync server and be done with it. It is theoretically possible but it is far from easy.
Tell me how to place the fucking tabs below the URL box.
Bless Firefox, and forsake them for hyped redesigns like these.
http://www.palemoon.org/
Switched from Firefox to Pale Moon because of Version 29 and haven't looked back. It is excellent.
-- For immediate release --
Firefox version creates puzzle for physicists
Firefox's rapid release schedule attained a new height yesterday when two consecutive Firefox versions were released 4*10^-44 seconds apart, less than the Planck time of 5*10^-44 seconds. "This should be physically impossible", said a prominent physicist, "this delay is too short for anything to happen, even at the subatomic level." Some skeptics speculated that the Firefox versions could have been designed in parallel and merely released 4*10^-44 seconds apart, but careful analysis of logs show that this is not the case and that a full development cycle occurred between the two releases. "We have a mystery on our hands", concluded the physicist.
Why don't they just randomize the user interface every time you start the program? I've spent over a decade getting used to things being in certain places with FF. Each version shuffles things like rearranging the furniture in a blind man's house. I have to put things back where they were so my muscle memory still works. I still go for View/Page Source - it's been that way for many years. Why change it? What does it accomplish to change it?
So, do the people who write this software not use it themselves? Do they not have muscle memory? Do they really re-learn where everything is every new release?
I mean, why? Why rearrange everything and trash the user interface? There's no reason for it. I don't understand. I can't process the idea that they just go in and trash everything for no reason.
I don't understand. I am not sure I want to understand. This is crazy, so should not make sense.
Most UI designers these days are hipsters. They don't give a flying fuck about usability. All they care about is making a UI that's trendy. It's totally cool if it's trendy but isn't actually usable. Usability is irrelevant to them.
Firefox is just one victim among many. They've fucked up Chrome from the very beginning. They've fucked up GNOME 3. They've fucked up Windows 8 and Windows Server 2012. They've fucked up iOS 7. They're in the process of fucking up OS X 10.10. They've been fucking up web design for a great many years now.
Hipsters are a disease that infects software projects. Once you understand that, then what has happened to the UIs of these formerly-great software projects makes perfect sense. It's much like the plagues that ravaged Europe centuries ago. A small hipster infection can spiral out of control and can destroy even the most robust and usable of software systems.
At the rate they're going, they'll probably emulate IE's look by version 40 (around next week)
I've got better things to do tonight than die.
It's totally hilarious how almost EVERY SINGLE PERSON outside of Mozilla who has had to use Firefox 29 has totally hated its UI. The most positive responses I've seen so far have been from people saying that they only kind of hate it. For each response like that, I see hundreds more from people who absolutely, indisputably, completely hate it to its very core!
I think this is funny as funny can be. The Firefox UI designers have created something that's universally hated! It's not just a little bit of hate from a few people here and there. It's total, unmitigated, unrelenting hatred for the Firefox 29 UI! LOL!
My betting is that the top dogs at Mozilla have been paid handsomely to shutter Firefox and make the transition to Chrome as smooth as possible. Firefox has really been Google's project for a long time now, in financial terms, and they don't need it any more.
Who says people like it when Chrome did this. Many of the people who hate what Firefox is doing also strongly dislike Chrome.
Firefox's share is plummeting
While I am not quite as vehement about it as you, I agree to some extent. Firefox has been trying to Chrome-ify its interface, and it sucks. It needs to go back to its roots.
And goddamn Google for harming it. Firefox is our last best hope for a non-intrusive, "independent" browser. Firefox needs to start looking -- HARD -- for better outside funding.
I'm at my Nevada vacation/retirement place for the first time since migrating my laptop from Ubuntu 12.04 LTS to 14.04 LTS. This dragged in Firefox 29.0 ("... Canonical 1.0").
The place only has dialup Internat at about 38Kbps. (Somewhat higher speeds are available at substantial cost, which doesn't make sense untlil we're here for more than a couple weeks a year.)
Web browsing was barely usable at this speed by using a few tricks. The most effective one was to configure Firefox to not load images until/unless I wanted to look at them.
When I got out here last Friday I discovered that firefox 29.0 no longer has the radio button in the preferences/configuration menus. An hour or so looking at about:config didn't turn up anything likely-looking, either.
Without this feature, "surfing" the current image-heavy web pages is essentially impossible. Even trivial pages may take a couple minutes to a half-hour to load. PER PAGE.
Did the Firefox crew restore the feature for 30.0? (Or does anyone know where it was hidden, if it still exists on 29.0 and 30.0?)
Developers breaking important features (that THEY don't use) while "improving" products is a real problem.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
The "useless" toolbars are useful to people who understand toolbars. The pointless changes to the firefox UI are a big "fuck you" all the sane users.
Go use chrome if you want chrome. Some of us don't use chrome because the chrome UI sucks.
Looks like the developers picked the wrong week to stop sniffing glue...
Do not look into laser with remaining eye.
Pale Moon Windows version
Pale Moon Linux version
Pale Moon has a 64-bit version. The 64-bit Pale Moon uses the Firefox add-ons; there are no problems except with some unusual add-ons.
Why do they release Firefox 30 for Android in the Play Store BEFORE it is even on their own FTP server
Life exists outside of Google, you know...
Move Sig. For great justice.
Did they fix the memory-hogging bug that causes instability? No.
See http://www.ghacks.net/2014/01/..., and it seems that FF is actually better than Chrome in memory usage!
Why are slashdotters so angry about the release schedule? Isn't this what is supposed to happen? According to ESR, release early, release often (and listen to your customers) is what makes open source great.
Is it really the release cycle, or is it that you feel that Firefox isn't listening to its customers. And who are the customers, really? The extension developers, or the people that use it on a daily basis to surf the web?
In my opinion, the customers are the people who browse the web. And if I look at it as that kind of customer, I am quite happy with Firefox and its release schedule. I get updates automatically and often and they often make the browsing experience better. Sure, sometimes something breaks, but they are keen to fix many of these problems.
-- The Internet is a too slow way of doing things, you'd never do without it.
Someone always mentions this mysterious, vaguely defined bug in every /. discussion of Firefox but my understanding is that all the major memory issues were fixed long ago. I certainly never have problems these days.
Can you be more specific? A link to the Bugzilla page or a forum thread perhaps?
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC