It's my theory once a well-crafted enterprise application becomes very successful it bloats up until design-by-committee is necessary.
From that point on it becomes an unusable disaster.
“Hey we got $so_many million dollar client who wants to use our product but they want to auth with their AD and can’t use our three other SSO options.”
And thus was born the company’s pluggable directory over VPN connector and auth strategy.
Still, salesforce can sell and that's how it got where it is.
You're right, if I'm using something as simple as Zoho, Streak, Insightly, Close, Pipedrive, etc.
But thats precisely my point - the greater the complexity of the application the more of the "nightmare of an API/UX". Have you ever worked with DynamnicsCRM? NetSuite CRM?
> It reeks of different services consolidated via acquisition (or one-off services kitbashed together), and adding slack to the mix will just add yet another variation to the existing APIs.
That's not how this usually works. Heroku is still running just fine and isn't a messy bunch of APIs since they were acquired. SFDC will likely just sell Slack into their enterprise clients and let it be.