Multiprocessing (Electrolysis aka e10s) hasn't been rolled out to all Firefox users yet - but Mozilla is preparing for new big changes in the Firefox architecture which they call "A Quantum Leap for the Web". They are planned to be available by the end of 2017. They are working on a next-generation web engine for Firefox by implementing components of the Servo engine which in turn is written in the Rust language. The high performance of Servo was already confirmed by a Google employee earlier this year. And the Rust code will make Firefox a much more secure browser than today. More info about the Quantum project on this Mozilla wiki site and on Bill McCloskey's blog. EDIT: A graph that illustrates the superior performance of Servo is on gHacks.
Sounds good to me, because I came to the conclusion that Chromium based browsers suck. Vivaldi, Opera and Chrome are all flops. What FF needs is not only a better browser engine, it also needs a better GUI, and a way better bookmarks manager. Better security would be nice, but I hope the new multi-process browsing feature will not make it even more bloated.
Blink as a fork from webkit is complete different from mozillas gecko or servo/rust. at least stay calm and drink some tea. but - servo/rust will kick the known XUL UI of firefox, any extension based on XUL is not functional - thats why webextension were coming and those are common for firefox, chrome, edge. so these browsers are not that different in near future - at least google is already using the mozilla javascript engine which is the fastest in the world. the new servo-UI is based on html. Servo as the new engine is written in RUST https://servo.org/ https://en.wikipedia.org/wiki/Servo_(layout_engine) Samsung is in the game to use the new browser on ARM or android devices. more about RUST https://en.wikipedia.org/wiki/Rust_(programming_language) as far i understood RUST is more secure than other languages. early builds of servo are only available for linux and mac osx https://download.servo.org/
That's incorrect. Google Chrome/Chromium is using the V8 javascript engine, while Firefox is using SpiderMonkey (with IonMonkey as JIT compiler).
I hope they do something that improves the situation. One of my users at work yesterday called me to his desk because as he was inputting text into a text box, in Firefox, with 1 tab open, he was complaining of tremendous lag. We opened task manager and Firefox was using 1.2 GB of RAM. I installed Chrome and it used less than 20% of that. I don't really care for Chrome, but if Firefox is going to run that badly I am going to install Chrome for everyone and maybe ban Firefox. I don't have the time to spend on issues that shouldn't exist. I prefer Firefox, but they need to quit wasting time on these side project that nobody cares about, such as attempts at an OS for phones, etc.
The one thing that makes Firefox run really badly is Adobe flash player. Really. Bad. De-activate flash and Firefox is FREE again. I like the way Firefox handles bookmarks. Just have to remember to back them up when needed.
You make a good point. Most of the Firefox issues I have had are because of Flash. It needs to die like Java.
Yes Rust is interesting (from security point of view). When new FF has electrolysis and low rights sandbox and is based on Rust, I might even try it in 2017, 1018, 2019 (it will probably delayed, like all Mozilla stuff)
It likely would, in at least some ways. Then again, there are multiple aspects to security and what qualifies as "secure" will differ. Especially when one is considering security at the browsING level vs the browsER level. A browser can offer excellent, theoretically even perfect, immunity to common programming mistakes and penetration and tampering. Yet at the same time score very low marks in other areas. Due to it being difficult to reliably capture traffic (and verify it is safe) and/or block traffic (deemed inappropriate by the user/admin) and/or disable browser or web features (which create a security issue in a given application). Whether the Firefox of tomorrow actually is more secure than the Firefox today will depend, in no small part, on its control/customization and extension [API] features. I hate to say it, but I think Mozilla (and every other major browser developer) will NOT get these aspects right without considerable active input from outside developers and users. Truly good end-user security (especially on the infosec side) and control of experience conflicts with too many business models plus career paths... and the bias of most browser developers is to want to create ever richer web features and out-of-box behavior that can't/won't be "broken" by users... and the bias of many developers these days is to want to pilfer telemetry from users, force experiments on users, etc. I really hope that extension developers and more sophisticated users can muster enough participation and success to offset such factors. Helping to achieve a final product that is configurable/flexible enough to serve the entire user base.
I've been using FF for many years and have installed it on friends' computers - and I've never seen this behaviour. This is certainly not a general FF problem but a specific one caused by, e.g., a corrupt profile or whatever. They've already given up that.
That's certainly unusual. I understand you don't have time for this stuff, but it would be interesting to know how Firefox got into that state; perhaps a misbehaving extension?
i got bad news for you https://github.com/nodejs/node-v0.x-archive/wiki/ECMA-5-Mozilla-Features-Implemented-in-V8 current is ES6 https://developer.mozilla.org/de/do...in_JavaScript/ECMAScript_6_support_in_Mozilla https://nodejs.org/en/blog/ but yes, bad formed sentence - google is still using mozilla code. that was part of the contract between those before mozilla changed to MS Bing/Yahoo/yandex.
It should be tab-based and bookmarks should be easier to manage. When bookmarking a site you should be able to instantly add a keyword to it. Believe me, compared to other bookmark managers it sucks.
Great news: Firefox 57 Nghtly for Windows contains the WebRenderer from Servo (disabled by default)! Note, though, that you won't see any performance gains yet as the rendering is still done in Gecko and the pixels are copied to WebRender which is very slow. The rendering features will be converted to WebRender step by step, so that the users will notice performance gains moer and more in the coming future. The integration of WebRender in Firefox is a big milestone for the Quantum project, indeed.