|
|
|
|
|
by gcp
3224 days ago
|
|
It's not "throwing toys out of the pram" when add-on developers are forced to rewrite their entire code every damn year, and this time using an incredibly limited API from goddamn Google Chrome of all places. It's one or the other. Either the API gives very deep control, and it must evolve as the browser evolves, or it does not, and it can stay stable. Experience says that Firefox was on the wrong side here by offering complete access, thereby either blocking the browser to evolve, or forcing add-on authors on a compatibility treadmill, effectively getting the worst of both worlds. Maybe it's possible to do better. But we haven't managed to do so, and neither has our competition. So it's probably not easy. |
|