SoylentNews is people
SoylentNews
From Firefox's faster, slicker, slimmer Quantum edition now out
[...] Collectively, the performance work being done to modernize Firefox is called Project Quantum. We took a closer look at Quantum back when Firefox 57 hit the developer channel in September, but the short version is, Mozilla is rebuilding core parts of the browser, such as how it handles CSS stylesheets, how it draws pages on-screen, and how it uses the GPU.
This work is being motivated by a few things. First, the Web has changed since many parts of Firefox were initially designed and developed; pages are more dynamic in structure and applications are richer and more graphically intensive. JavaScript is also more complex and difficult to debug. Second, computers now have many cores and simultaneous threads, giving them much greater scope to work in parallel. And security remains a pressing concern, prompting the use of new techniques to protect against exploitation. Some of the rebuilt portions are even using Mozilla's new Rust programming language, which is designed to offer improved security compared to C++.
Also at: Firefox aims to win back Chrome users with its souped up Quantum browser
The fastest version of Firefox yet is now live
(Score: 2) by KritonK on Thursday November 16 2017, @02:12PM
Indeed, it has migrated. Not much of a surprise, as it was already working in chrome. It probably needed few, if any, changes, to run in firefox.
As to which is better, that is a matter of preference. With noscript, I have enabled "Temporarily allow top-level sites by default / Base 2nd level Domains", and most sites work as intended, with the possible exceptions of embedded multimedia, if they are served from another host, e.g., youtube, in which case I only need to allow that host. With uMatrix, I have to micromanage every single site, specifying not only the hosts from which it is allowed to use resources, but the kind of resources it is allowed to use as well. Theoretically, one can come up with the minimum amount of permissions that one needs to enable, in order for a site to work. In practice, this is way too much work, not to mention that one needs to actually understand what all these kinds of resources are. With uMatrix, I find myself enabling all the resources of host after host (example.com, cdn.example.com, images.example.com, whydotheyusesomanyhostnamesat.example.com, etc.), then doing it again, as some resources need to be enabled individually, with the process often getting out of hand, as the list of hosts keeps increasing, each time one is enabled. Thus, I prefer using noscript.