7 ms·
The XPCOM-based extension mechanism was mostly dropped (we still use it internally) See, that's the rub. Many of us would choose to have add-ons that break ev
by causality0 6y ago
The XPCOM-based extension mechanism was mostly dropped (we still use it internally)
See, that's the rub. Many of us would choose to have add-ons that break every time the browser updates, or delay browser updates until our mission-critical extension is updated. You didn't give us that choice though. You said "do it the way we want you to do it or piss off." Looking at Firefox's 3% market share, most of us chose the latter.
- cinquemb 6y agoSome of us didn't care because we were already running our own forks and could deal with the old way and the new way.
- Yoric 6y agoOur experience is that add-on developers didn't like that. Only the few add-on developers that actually made money from their add-ons could afford to rewrite their code every 6 weeks. Clarifying the article.