4 ms·
They're clearly adding APIs that they think are necessary, vs the ones addon developers actually need and clamour for. We've seen this in the entire process. Mo
by andrepd 9y ago
They're clearly adding APIs that they think are necessary, vs the ones addon developers actually need and clamour for. We've seen this in the entire process. Mozilla is not interested in listening to the actual needs of the developers. They just have their own idea of "brand new cool features" and they're gonna roll with it. Disappointing.
- DiThi 9y agoPart of the reason is that most users of some popular addons don't participate in the open source community, reporting bugs, commenting on them to add details or tell why are they important, etc.
- pbhjpbhj 9y agoDo Mozilla contact the creators of the most popular addons, they could serve as a useful proxy for trying to get direct input from inexperienced users.
- DiThi 9y agoThey probably do. But Firefox addons is a long tail. There are many addons that would qualify as "popular" but Mozilla wouldn't be able to contact them all. So they have to measure not only popularity, but also if the community cares about that addon. I had many addons installed that I don't use, synchronized across devices: They may count as "popular" but it doesn't reflect the actual community and usage.
- detaro 9y agoAnd if they do, they don't communicate in the way Mozilla would like them to. Users can't say much more than "I want X to be possible", add-on developers can comment on what API they'd like, but after a short initial wave of that these things tend to be treated as noise even if they are presented very friendly, because the actual dev-work that is necessary in the end is guided by other principles these parties can't contribute much to. And it's really difficult to guide that in a way that doesn't make people feel bad.
- Vinnl 9y agoWhat do you base this on - your own intuition of what you think add-on developers need? Because they've been interacting with add-on developers a lot.
- usrusr 9y agoUnfortunately, some of that interaction was barely more than a slightly more polite form of "get off my lawn" whenever it came to add-ons about tweaking the UI. Mozilla deliberately removed a lot of customizability, but instead of being open about it they made addon developers the scapegoat, sending unhappy users their way while blocking requests for replacement APIs with "you are not supposed to do that kind of UI tweaks anymore". After a decade or so of encouraging UI extensions whenever someone suggested advanced UI features, this is a bit lame.
- Vinnl 9y agoI'll give you that the removal of some customisability is deliberate, but not that it's not interested in listening to the developers. It just has a different opinion than some of them on what should be allowed. That said, there's also a lot of customisability that simply hasn't been implemented yet. I'd name e.g. hiding of the tab bar where Mozilla is clearly seeking a compromise between the potential downsides of removal of UI elements by add-ons and how useful it could be. It just takes time to make it happen, but luckily, Firefox 52 is still an Extended Support Release for quite a while.
- usrusr 9y agoHiding the tab bar to replace it with a full custom implementation, instead of modifying the stock tab bar? That might be reasonable, if APIs are sufficient to fully reimplement all features of stock, with no corners cut. If it's just "done, tab bar hidden, here is a sidebar for you to play in, have fun", then it would be full-on "the emperor's new extension API".
- Sylos 9y agoBesides what the other commenters already responded, APIs don't just fall from the sky over night. And especially the APIs that you refer to, are just not trivial to write at all. Just because add-on developers yearn for super powers, doesn't mean that Mozilla can provide this as quickly as lesser super powers.