Hacker News new | past | comments | ask | show | jobs | submit login

It could never deploy multi-process with XUL cruft. Then the argument would be that Firefox is too far behind. You can never win everybody.



"e10s compatible" add-ons were as fully-featured as the "original" XUL add-ons and did not interfere with multi-process at all. For instance, VimFx was e10s compatible and could even run with Firefox Nightly (which allowed "legacy" add-ons), without disabling multi-process, until about Firefox 65(!), without major changes.


Taking away XUL is not the problem. Leaving users with a crippled replacement is.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: