3 ms·
I really feel both sides of this. On the one hand, I like customizing things, and I love to see users getting involved in platforms they love. On the other, I s
by wpietri 8y ago
I really feel both sides of this. On the one hand, I like customizing things, and I love to see users getting involved in platforms they love. On the other, I see how responsibly providing APIs is a big long-term burden that can prevent internal innovation.
I was talking a while back with some Mozilla people about the move from their legacy API [1] to WebExtensions [2]. It was a giant pain, but their old API exposed way too much surface area in ways that were too closely tied to the original implementation. The way I heard there were significant ongoing costs in trying to maintain the old API and support popular extensions while trying to improve the underlying tech and the user experience. So I get why Slack is very reluctant to expose API surface area, especially for the UI.
[1] https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Legacy_add_ons https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Leg...
[2] https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
- dotancohen 8y agoThat is because an API should express high-level concepts, not low-level implementation. Just as the new WebExtensions API does. And as any hypothetical Slack API should.
- apotheon 8y agoIn deprecating functionality necessary for the extensions that made Firefox worthwhile for me, though, the reasons to prefer it over other browsers evaporated.
- deleted 8y ago[deleted]