4 ms·
Its not just Chrome, Firefox is planning to deprecate it as well (https://www.bleepingcomputer.com/news/google/chrome-and-firefox-developers-aim-to-remove-suppo
by shscs911 7y ago
Its not just Chrome, Firefox is planning to deprecate it as well (https://www.bleepingcomputer.com/news/google/chrome-and-firefox-developers-aim-to-remove-support-for-ftp/ https://www.bleepingcomputer.com/news/google/chrome-and-fire...). Relevant Bugzilla ticket (http://bugzilla.mozilla.org/show_bug.cgi?id=85464 http://bugzilla.mozilla.org/show_bug.cgi?id=85464)
- syshum 7y agoNot Surprising given Mozilla Stance to duplicate and support everything Google does in a effort to chase relevancy again Mozilla has lost the ability to be an independent protector of the Open Web
- qzx_pierri 7y agoIt's sad because they don't need to. Quantum is great, and you can remap your keybinds and use MaterialFox to get (almost) the exact same experience. Of course your average pleb won't go through this effort, but people need to know how good Firefox has gotten. And to the people who disagree: Firefox has always been great, but it often came with a lot of bugs and inconveniences. It didn't use to be as accessible. https://github.com/muckSponge/MaterialFox https://github.com/muckSponge/MaterialFox
- fucking_tragedy 7y agoHave they fixed the issue with excessive resource consumption when using Firefox on a Retina MacBook?
- insulanian 7y ago+1 I tried to switch to FF on multiple occasions, but it's a CPU hog on MacBook. Why is this issue ignored for so long?
- fucking_tragedy 7y agoBased on what I saw the last time I checked Mozilla's bug tracker, the issue has a low priority and no one is actively working to resolve it. From what I understand, it's a low level rendering issue.
- pcwalton 7y agoThat's not true. There was a roadmap posted yesterday and patches to begin to address the issue landed this week, including a new preference to opt into Core Animation. This is Markus' top priority at present. https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 Source: I wrote the initial version of those patches, though I think Markus has basically rewritten them all at this point.
- fucking_tragedy 7y agoMy mistake, I hadn't checked on the status in nearly a year. Glad to hear that progress is being made. Thanks for the update and patches!
- pcwalton 7y ago"Resource consumption" in the parent comment refers to power efficiency, specifically GPU blits. That issue has not been ignored. I don't know what "CPU hog" refers to; the issue is not about CPU usage.
- insulanian 7y agoIt's consuming ~20% CPU in idle on my machine (MacBook Pro Retina, 13-inch, Early 2015, 2.7 GHz Intel Core i5, 8 GB 1867 MHz DDR3, macOS Mojave 10.14.6)
- louiz 7y ago> Quantum is great, and you can remap your keybinds Please explain how. Since firefox 57 (quantum), there's precisely no way to do that properly...
- nudq 7y agoBy following Chrome every time Google wants to removes access to parts of the web not sufficiently encrypted (to thwart ISP competition for ads and data) or not serving ads (like FTP) Firefox is working to keep Chrome relevant. It has been going on for years.
- tacotime 7y agoWhaaat? They came for the RSS feeds and I said nothing... Bugzilla.mozilla.org is offline, here's a mirror: https://web.archive.org/web/20190520010425/http://bugzilla.mozilla.org/show_bug.cgi?id=85464 https://web.archive.org/web/20190520010425/http://bugzilla.m... and relevant quotes posted there (a year ago!): "I think we should mark this bug as WONTFIX. We have a vague plans of deprecating FTP completely in Firefox, there is no point in adding more code in this area." "Since we (sooner or later) would like to deprecate FTP completely, we should not add more code in that area to our codebase."