The idea: treat memory/CPU/battery efficiency as a major, visible engineering initiative, not a background cleanup task. I think this is genuinely one of the biggest levers Mozilla has for winning people back from Chrome.
Why I think this matters: there's a long running pattern of users reporting high RAM usage and multiple background processes even with just a few tabs open, going back years and still showing up regularly. At the same time, Firefox has been losing users. I don't think that's a coincidence. The people most likely to want an alternative to Chrome (privacy focused users, Linux users, people on older or lower spec hardware) are also the people who feel resource usage the most. So the easiest potential converts are the ones getting hit hardest by this.
What the idea actually involves:
None of this is a request to fix a specific bug. It's a request to make efficiency a stated strategic priority the way privacy already is, since I think it's the missing piece for actually converting Chrome users rather than just retaining existing Firefox users.