5 ms·

While some progress is being made, it worries me that it's taking so long to get this functionality into the release versions. I'm not suggesting it should be r

by epoch1970 10y ago

While some progress is being made, it worries me that it's taking so long to get this functionality into the release versions. I'm not suggesting it should be rushed out, of course. But the Electrolysis efforts date back to 2009, if not earlier. That's a long time to make users wait!

tetromino_ 10y ago
Electrolysis breaks extensions that use low-level APIs designed in the single-process era [1]. This breakage drew the ire of a vocal minority of Firefox users enamored of such extensions, and AFAICT that's the major reason why e10s has taken such a long time to get enabled in release. [1] https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox https://developer.mozilla.org/en-US/Add-ons/Working_with_mul...
cpeterso 10y ago
While the original Electrolysis work dates back to 2009, the project was put on hold for a couple years in the middle. Development resumed in mid-2013, as the archive of meeting notes shows: https://wiki.mozilla.org/Electrolysis/Meetings https://wiki.mozilla.org/Electrolysis/Meetings
AckSyn 10y ago
Why does this concern you? Mozilla, isn't as cavalier as Google as far as releases are. I remember a time in chrome's beginning it was horribly unstable but patched often. It was the lure of constant quick updates that kept a lot of people eager for the "fixes".
- verroq 10y ago
  Grandgrandparent: firefox is shit because it doesn't have feature X which causes it to crash if a single tab becomes unresponsive grandparent: firefox is building it parent: it tooks them 7 years and it is still not done? you: why do you care, who cares if mozilla updates slow? me: ???
nnethercote 10y ago
I heard a nice description of Eletrolysis that at least partly explains why it has taken so long: it's the single largest change that has ever been made to Firefox.

5 ms·

While some progress is being made, it worries me that it's taking so long to get this functionality into the release versions. I'm not suggesting it should be r

by epoch1970 10y ago

tetromino_ 10y ago
Electrolysis breaks extensions that use low-level APIs designed in the single-process era [1]. This breakage drew the ire of a vocal minority of Firefox users enamored of such extensions, and AFAICT that's the major reason why e10s has taken such a long time to get enabled in release. [1] https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox https://developer.mozilla.org/en-US/Add-ons/Working_with_mul...
cpeterso 10y ago
While the original Electrolysis work dates back to 2009, the project was put on hold for a couple years in the middle. Development resumed in mid-2013, as the archive of meeting notes shows: https://wiki.mozilla.org/Electrolysis/Meetings https://wiki.mozilla.org/Electrolysis/Meetings
AckSyn 10y ago
Why does this concern you? Mozilla, isn't as cavalier as Google as far as releases are. I remember a time in chrome's beginning it was horribly unstable but patched often. It was the lure of constant quick updates that kept a lot of people eager for the "fixes".
- verroq 10y ago
  Grandgrandparent: firefox is shit because it doesn't have feature X which causes it to crash if a single tab becomes unresponsive grandparent: firefox is building it parent: it tooks them 7 years and it is still not done? you: why do you care, who cares if mozilla updates slow? me: ???
nnethercote 10y ago
I heard a nice description of Eletrolysis that at least partly explains why it has taken so long: it's the single largest change that has ever been made to Firefox.