Being multiprocess doesn't help that much for most vulnerabilities.All those browsers are inherently more secure than Firefox by design which makes the nature of its vulnerabilities far more severe.
So you're switching to Chrome because Mozilla is implementing an add on system more like Chrome's?
I would never switch back to Firefox but I still use it as my video downloading browser. If this ruins the ability for me to use DownloadHelper to download videos from websites.
Look on the bright side, they'll finally be rid of that memory leak!
Compared to Chrome, Safari and Edge.
Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136
I don't want to have to compile an app myself to download videos. And does it work with all websites? And I mean all web sites. (Excluding DRM sites like Netflix and Hulu of course.) See thats what DownloadHelper is good at. I can get video from pretty much any site including most... alternative video sites.youtube-dl is what I use for almost everything these days. It's simple once set up and configured for most sites including RTMP streams. DownloadHelper is a great addon though, at least the last time I used it.
Being multiprocess doesn't help that much for most vulnerabilities.
It's more secure in the crypto sense, but it's a necessary condition more than a sufficient one. None of the browsers are within sniffing distance of being used for serious crypto, including Chrome. That is the end goal, though, which is one of the reasons (the other being performance) that FF is going there.
He's overreacting. Give it time to see how it shakes out.Well... fuck. If I wanted Chrome I would use Chrome, I want my add ons![]()
I don't want to have to compile an app myself to download videos. And does it work with all websites? And I mean all web sites. (Excluding DRM sites like Netflix and Hulu of course.) See thats what DownloadHelper is good at. I can get video from pretty much any site including most... alternative video sites.
youtube-dl https://www.youtube.com/watch?v=L6VxXGPifbE
youtube-dl -f bestvideo+bestaudio https://www.youtube.com/watch?v=L6VxXGPifbE
That's another issue altogether, one that Google are working on.
People are going to complain about Firefox becoming more like Chrome but that's necessary. Firefox is old and adding things like per-tab processes and a sandbox are proving really difficult and to my knowledge they still don't have an official 64bit release (only alphas). What was okay 10+ years ago when the only competition was IE is inadequate now. Insisting on using Firefox is a bit like sticking with Windows XP; it's horribly dated.
Firefox will also continue to support add-ons built using the high-level APIs provided in its add-on SDK, provided that they do not use XUL.
Firefox has been 64-bit on Unix-y systems (meaning Linux and Mac) for a while now. The 64-bit Windows builds have taken significantly longer, though they did just reach Beta. Given that 64-bit support on Windows lagging behind 64-bit support on Unix-y systems is a relatively common pattern that I've seen, I'm hesitant to fully blame Mozilla for it taking so long.
There have been 64bit variants of Windows since Vista (you can argue XP but model was slightly different). It's squarely on Mozilla.
You do realize Edge is just Internet Explorer 12, with all the baggage that entails, right? The only practical difference that I've found (in my admittedly minimal time using the browser) is that the User Agent String has reached new levels of asinine. I mean, look at this thing:
Code:Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136
Edge is pretending to be Chrome, which is pretending to be Safari, which is pretending to be Firefox. It's bad enough that all major modern web browsers pretend to be Firefox/Netscape Navigator thanks to decades old bad server code, but this is just getting ridiculous. Opera used to be the lone holdout, but that ended when Opera ceased to be it's own existence. No rational person should be looking at modern browser user agents and thinking "we need to go deeper".
That's another issue altogether, one that Google are working on.
People are going to complain about Firefox becoming more like Chrome but that's necessary. Firefox is old and adding things like per-tab processes and a sandbox are proving really difficult and to my knowledge they still don't have an official 64bit release (only alphas). What was okay 10+ years ago when the only competition was IE is inadequate now. Insisting on using Firefox is a bit like sticking with Windows XP; it's horribly dated.
You do realize Edge is just Internet Explorer 12, with all the baggage that entails, right? The only practical difference that I've found (in my admittedly minimal time using the browser) is that the User Agent String has reached new levels of asinine. I mean, look at this thing:
Code:Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136
Edge is pretending to be Chrome, which is pretending to be Safari, which is pretending to be Firefox. It's bad enough that all major modern web browsers pretend to be Firefox/Netscape Navigator thanks to decades old bad server code, but this is just getting ridiculous. Opera used to be the lone holdout, but that ended when Opera ceased to be it's own existence. No rational person should be looking at modern browser user agents and thinking "we need to go deeper".
Edge is a fork of of the trident engine with all the legacy crap removed. No baggage, less attack surface, that's the whole point. Also I'm not sure where your user agent rant is going, it sucks but whatever, it's not a security thing.
and Edge is a legitimately a new branch of Trident. It's not IE12.
The user agent string isn't really relevant anymore. It's for old content that check it for compatibility reasons.
Anyone doing modern websites correctly will be feature-testing, not checking the browser agent string.
Edge/12.10136 (Windows NT 10.0)
Will gifs still work properly?
Calling Edge a fork of Trident is rather silly, and is more a marketing move to separate the browser from IE. If Microsoft actually intended to release a "true" IE12, then I might be more convinced. As it stands, Edge is just the next natural evolution of Trident. It may be a somewhat bigger upgrade than usual, but Trident desperately needed upgrading. And yet, despite all of the work Microsoft has done on Edge, it still lags pretty for behind most browsers regarding standard support. I suppose my original comments were a bit unfair, since they have actually dropped support for some auxiliary things which really needed to die long ago, but it clearly is still the same core engine.
Why don't you tell that to Google, who won't allow me to upload images to Google Photos from my Wii U unless I use an alternate User Agent String. Or Netflix, who won't let me watch videos on Linux unless I tell them I'm using Windows.
I'd love to live in your fantasy world where User Agent Strings don't matter anymore, but that simply isn't the case. If they truly didn't matter anymore, then Edge's User Agent would look something like this:
That is what a User Agent String is supposed to look like.Code:Edge/12.10136 (Windows NT 10.0)
Your assessment needs more factual grounding. Start here: http://blogs.windows.com/msedgedev/...birth-of-microsofts-new-web-rendering-engine/
So you're switching to Chrome because Mozilla is implementing an add on system more like Chrome's?
For the security risk of staying on an old browser version, would it be viable to run a browser through a sandbox every time? If you changed the shortcut to go through something like Sandboxie, my first guess is that you'd never notice the difference.
That's Google doing things incorrectly.
The User Agent String became useless all the way back in the mid 90s. Browser vendors didn't take long to 'cheat' it by putting other browser names in there, and some people still cling onto using it, even though they shouldn't be. Even Opera shipped with a drop down menu to change your user agent, standard.
If it has a list of supported sites, it's not going to work for me. DownloadHelper works on all sites no matter what as long as there's no DRM protection. (Which is rare)I just use the Windows binary from the download page and stick it in a path the system can see, along with setting a default download path in a config file. Then it's as simple as pasting in the link I want and it'll grab it. List of supported sites.
This is why I use an older version of firefox where my add-ons still work and is not a resource hog.
Do you want viruses? Because that's how you get viruses.
.If I wanted Chrome I'd switch to Chrome ya jackasses.