Requiescat in pace, dear friend.
The writing is not yet on the stone, but I see it on the wall.
I'll visit from time to time, as I come to see SeaMonkey.
Code from a project billed as “the future of developing add-ons” in Firefox will debut in early 2016. The code will let extensions written for Google’s growing Chrome run, supposedly unchanged, in Firefox. The WebExtensions API, announced in August and currently in alpha, is expected to see daylight in March 2016, with …
"Fellow Lizard People,
yep, NoScript is the real (the ONLY reason) I'm still using Firefox..
it's sad how they're slowly changing it from a cutting edge browser with real identity and individuality into what feels like (functionality wise) just another skin for Chrome..
Firefox, quick hint, stop trying to be a chrome clone.
Wondering why more & more firefox users are swapping to chrome?
As you keep ripping out, or at best drastically changing distinctive firefox features / functionality (& yet not fixing longstanding bugs such as excessive idle disk access) to be more & more like chrome, lots of people just think, I'll switch to chrome anyway as firefox will soon be indistinguishable from it as its lost its USP & chrome is less resource intensive (mostly).
Mind you; if Firefox manages to support Developer Mode and local extensions without continually nagging the users that they are enabled, they could actually steal some share from Chrome.
Or - because I do understand why the warning should not be removable - just demonstrate a less intrusive, less mouse focus stealing, way to show that and it might encourage Google to follow suit.
The Mozilla Foundation have always been the nice guys of the web, and I've used Firefox since the early 2000s (with fond memories of "Cookies are delicious delicacies" - in itself a hat-tip to Netscape).
I did have a spell where I moved to Chrome because everyone was telling me how much quicker and more efficient it was, but to be honest I noticed no difference whatsoever (benchmarks are rarely a true reflection of real-life usage scenarios) so moved back within a few weeks.
Call me paranoid if you like, but I'd rather use an independent browser than one run by a monolithic corporation such as Google, Microsoft or Apple, each of which have their own longer-term agendas.
The very fact we have such a choice is the important thing, and long may that choice continue to exist. away from the dark early days of the web with the massively dominant IE5/6 market share.
Same here really: I think it will be a very dark and sinister day for the internet if Google gets to own (and control) the entire stack, from the entry point (search) through the content (YouTube, etc) to the client used to access it all (Chrome).
Netscape gave us a choice against Microsoft's dominance. It's not just for nostalgia that its progeny Firefox - for all its warts - should be supported and improved to ensure that some choice remains in a Google-dominated world.
Ditto except for sniffing other browsers. I have no complaints with Firefox. I don't get the reminders that others are remarked about, but I do get all the add ons I want including NoScript, Disconnect, Privacy Badger, and HTTP Nowhere. Speed is not an issue for me either with all the ad and tracking stuff blocked.
Like others here, I stick with Firefox mainly due to NoScript. Combined with some other add-ons, it's allowed me to use the browser the way I want to. Chrome is not something I'd ever want to consider, bearing in mind Google's invasive behaviour is built into it. God knows what's in Edge now that MS seem to want all our data as well. Safari isn't usable on anything other than a Mac, and Opera seems like a Chrome Clown.
I will keep using Firefox, even if an older version, for as long as I can. Outright speed isn't all that internet browsing is about*. But, the day that the add-ons that I use become sufficiently compromised, is the day I will have no choice but to find something else. Maybe then I'll check out SeaMonkey.
*NoScript actually speeds up my browsing on FF, mainly because it allows me to choose to block most of the shit from coming down the pipe except the most essential stuff for a web page to work.
I'm really looking forward to this. I've had quite a few requests to port my Chrome extension over to Firefox but as much as I'd love to do so I simply don't have the time right now. This kind of functionality, assuming it works as advertised, could potentially save me dozens of hours or more.
.. who prefers Firefox Developer Tools?
Chrome's developer tools have a few useful features (can't think of them now) but the in-built developer tools of Firefox are more useful: 3D view of the DOM, CSS editor that allows new style sheets to be created, easy to use HTML editor and so on. I see no benefit to using Chrome's developer tools over Firefox developer tools but plenty of benefits to using Firefox's developer tools instead of those provided by Chrome.
I do hope Autofill Forms continues to work when Firefox introduces its new extensions API. Looked for a similar form filler for Chrome but not found suitable substitute yet.
I care quite a bit about the UI and the features - desirable or otherwise.
- Noscript & flashblock, certpatrol.
- A separate url and search box. When I type in a word into the URL bar, please assume its a host name rather than going off to <searchengine> to search for stuff. That is really annoying (I'm looking at you IOS Safari)
If I haven't specified a protocol, try https and http in the background. Give me an option for one or the other and to default to one or the other, if both work.
- don't autofill unless I ask you to. Don't even pre-fill boxes for real (maybe just pretend) because browsers can send back data before the submit button is pressed.
So no, I don't trust Chrome, even if I have Chromium installed for occasional use and even if I think there's a chance it is technically a better browser (I like its sandboxing).
Firefox it is for the foreseeable future.
Firefox for Windows is now available for 64-bit. Until the developer edition for x64 was announced I had been using Waterfox, which felt a lot faster than the 32bit Firefox builds from Mozilla. However, switching to the new Firefox dev edition made things so much smoother, with browser loads finally somewhat distributed across multiple CPU cores.
Some posters above have mentioned keeping Firefox around for AdBlock+ and NoScript, a sentiment with which I can agree. Surprisingly an even bigger reduction in page load latency came from replacing AdblockPlus with uBlock Origin. With these two changes my browsing experience has improved tremendously. If these improvements carry over into Mozilla's other builds then performance cannot be blamed for Firefox's ultimate failure or success--that will, in the usual sort of fickle, insipid human display of vanity, come down to ita perceived fashionability. Products seldom succeed based solely upon their technical merits.
well, tried Ublock, but it is not as easy to use as adblock...It is a bit like stepping back to a MUCH simpler interface!
give it a make over to look like adblock, I may try it.. It may seem faster if you have no other addons, but..
This is awesome!
I moved to Chrome because it allowed me to make extensions with complete ease.
All attempts at that Ive seen in FF so far have been buggy and just crappy.
If they pull this off thats one less reason to stick with chrome, then its prolly down to web inspector.
I love the Mozilla Foundation for all they have done for us (MDN is my bible), really hope this helps them get back some users...maybe even me one day.
Biting the hand that feeds IT © 1998–2019