Re:Bye bye BetterSlack
by dotancohen on Thursday August 30, 2018 @07:30AM
(#17875793)
That 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.
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/Leg...
[2] https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...