4 ms·
And if those features happen to never be implemented? I really think it is a bad practice to force adoption of a new API that can't fulfill the same functions
by mbrumlow 7y ago
And if those features happen to never be implemented?
I really think it is a bad practice to force adoption of a new API that can't fulfill the same functions as the previous one.
Nobody would be here talking about this if they just made the new API without breaking add blocking (useful add blocking), and then forced people to move.
Even more so given that it looks really bad when your main goal is to serve people ads.
- CmdrKrool 7y ago> I really think it is a bad practice to force adoption of a new API that can't fulfill the same functions as the previous one. I agree, which incidentally is the reason I switched from Firefox to Chromium a couple years back as Mozilla dropped XUL extensions for their own development convenience, toward an ideal of cross-browser extension compatibility, and in hoping to win over Chrome users by making Firefox more alike in both looks and performance. How many of those motivations have changed, and do we know that Mozilla aren't actually going to follow suit with a similar restructuring of APIs some time after such changes have settled into and been normalized in Chrome?