Slashdot Mirror
Firefox 43 Arrives With 64-bit Version For Windows, Android Tab Audio Indicators (venturebeat.com)
An anonymous reader writes: Mozilla today launched Firefox 43 for Windows, Mac, Linux, and Android. Notable additions to the browser include a 64-bit version for Windows (finally!), a new strict blocklist for the browser's tracking protection feature, and tab audio indicators on Android. "There is, however, a bit of a caveat. Firefox 64-bit for Windows has limited support for plugins. Certain sites that require plugins and work in Firefox 32-bit might not work in this 64-bit version. But Mozilla doesn’t see this as a big problem, and says it is by design. After all, the company plans to drop support for NPAPI plugins in Firefox by the end of the year (though it will keep Flash around). Mozilla has just over two weeks to deliver on that promise." Here are the changelogs: desktop and Android.
Netscape has never been able to actually pay attention to what the users of its browser want. The new netscape, which you kids know as mozilla, is behaving 100% EXACTLY like the old Netscape ...
Firefox stopped being the best browser right about the time ie6 was deprecated. Yes, IE sucks, but FF sucks more actually.
This is all simply an extension of their inability to write a browser.
Not that they don't have some talented developers, they do ... but they just let them do whatever they want and have no focus on actually delivering something users want, so they keep coming up with all these retarded silly side projects and all these retarded bloated 'features' in firefox ... its only taken them 15 years to realize doing everything in XPCOM and JavaScript was a fucking stupid idea.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Which about:config preferences do I have to mess with to disable all the unwanted "features" in this version?
Unfortunately, it's the browser with the best implementation of NoScript. Thus, it is indispensable.
For me it is "Tree Style Tabs". Unfortunately, Mozilla plans to phase out the current extension framework in favor of something more along the lines of what Chrome does - so we'll both be screwed shortly. But in the meantime, Firefox's killer feature is its extensions.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
I won't use Chrome again until there is a reliable way to prevent extensions from auto-updating. I got tired of finding out "surprise!" that something that worked yesterday is no longer around because the extension has gone "pay".
What's wrong with acting exactly like how the older product worked? Newer is not better. A web browser is simple, it doesn't need biweekly changes to its UI. the old Netscape was just fine. Web browser as an application platform is the dumb idea. DRM in browsers is a dumb idea.
If firefox goes away then there is literally nothing left. A browser must support adblock and noscript, as well as general purpose plugins.
Chrome has all the disadvantages of Firefox, but from Google. Rapid fire unnecessary updates unrelated to security, dropping of support for plugins, development oriented towards developers rather than users, frequent kissing of advertising butts, etc.
So I'm a bit of a Firefox loony, maybe visible from my post history.
I've been a "hardcore" web browser, ever since using NetCaptor (a shell replacement for Internet Explorer which offered tabbed browsing, IIRC the first tabbed browser)
Anyhow, I like Chrome performance but GREATLY dislike my ability to customise it, specifically tab control (which tab will the app go to if I close the current tab, left or right? will a new tab open in the foreground? what if I middle click a URL, foreground / background?)
I've loved FireFox for years, but the 32bit builds are frankly, unstable dog shit for me, crash extremely regularly. .5 to 3 seconds. Clicking some buttons can be slow to react. Generally after a few seconds of switching into a tab though, it responds /mostly/ ok (Don't even think about Flash Video in a tab though, I just put that into Chrome and drop it on to a second monitor)
I switched maybe 12 to 18 months back to WaterFox, some dude compiling up the 64bit code of FireFox and packaging it. It runs exactly the same as FireFox for me, all plugins work and it virtually never crashes. Problem is, as an "extreme" browser (anywhere from 30 to 300 tabs open at a time) FireFox / WaterFox can get slow.
REALLY slow, CTRL-TAB to change tab? Can take
I just checked, I currently have 393 tabs open (working on getting this down) of all the things I'm currently reading / researching etc.
So to get to the point,..... :/ the one surprising thing I'd say is it's stable as heck for me. I notice almost no different between WaterFox and Nightly 45.
I was hoping that E10s (Electrolysis, multi-threaded Firefox) would fix my problems, when it finally got better. I installed said nightly builds and I have to report that sadly. The performance difference between WaterFox and standard 64bit FF Nightly 45 (with E10s) virtually identical to one and other.
I've confirmed E10s is on and being a nerd but without programming skills, I kind of blindly, optimistically figured, hey, latest builds, 64bit official, e10s, I bet if anything nightly might be less stable but fast as hell!
Not in the slightest, it really is virtually identical
Note: I did try this, with and without my plugins to make FF nice and usable.
For what it's worth, my #1 plugin I can't live without is Tab Mix Plus. That fine control on tab behaviour and the fact I'm an extensive keyboard shortcut guy, makes the browser far, far more usable for me. I'd say I browse between 4 to 12 hours a day, every day.
Please note, I do COMPLETELY realise that running in excess of 30 to 50 tabs is ridiculous, but back 6 years ago, I could do this under FF32 and while it was unstable, the performance of the primary UI for FF was fine.
All I want the damn code to do is HIGHLY prioritise the current tab in front of the user and HIGHLY prioritise the ability to switch tabs, preferably the ones nearby (left, right of the active tab) - the process of going between them shouldn't be slow. Considering I've got 4 threads at my disposal here, it's a bit of a shame.
At least it's stable and at least I can control the behaviour and look, how I like. I think Googles stubborn attitude towards Chrome is ghastly, personally.
The version number almost says it all. How can you get excited about a new Firefox release with any feature, when it's just another rapid release. It could have true hard AI and no one would notice any more. It would get lost in the staggeringly mediocre array of non-features nobody wants, forced UI changes, broken addons, and developers that decide they know more about what people want than the users do.
Firefox adopted Google's rapid release cycle on a project that it was neither technically nor culturally suited for. One has to actually admire their dogged persistence to holding course in the face of what is an almost a completely unified chorus of "WHAT THE FUCK PEOPLE?!?!?".
I recommend Palemoon. A fork of the previous Firefox LTR, it has refused to add features unless they make sense, is compatible with most addons, and has its own growing body of its own addon developers that are quite loyal to the project for the simple reason that the project remains loyal to them. That's not to say that it's a static browser. Just one that took the best of what Firefox was and decided to continue in the direction of sensible goals and not alienating its user base.
Same problem every other 64bit browser has that uses plugin made under designs from 20 years ago
But with 64 bits, Firefox will finally be able to address all the memory it uses!
Firefox suffers from the syndrome known as "Bikeshedding".
They long ago abandoned what should be their core focus -- fix bugs, improve performance and implement new standards as needed (CSS 3, HTML 5) -- and have focused instead on endless tinkering, completely destroying the UI and a parade of useless new "features".
I'm all for fixing the security problems. Moving stuff around on the UI has nothing to do with security.
NoScript is an extension, not a plugin. Those are two completely different kinds of addons. Mozilla's quite particular about that distinction.
Extensions are the things we all know and love, like uBlock, NoScript, GreaseMonkey etc. Plugins are things like Flash, the Java web plugin for running applets, Google Update, Silverlight, and so on. For the most part we really don't need plugins.