From that perspective, the problem isn't so much the proliferation of service providers but rather the proliferation of aggressively proprietary protocols. By that I mean services that don't merely fail to document and stabilize their protocols, but actively attack and undermine third-party clients. Some of them outright ban third-party clients in their ToS, some theoretically allow third-party clients but impose API limits that are unusable at scale, and some deliberately make API/protocol changes to break clients created via reverse engineering. Anything short of that gets some kind of native Linux client if it gets popular.
That stance, in turn, is driven by business considerations that would probably be a huge tangent to discuss here. But it's important to keep in mind that this isn't just how things have always been; it's a relatively new trend, and trends can reverse.
That stance, in turn, is driven by business considerations that would probably be a huge tangent to discuss here. But it's important to keep in mind that this isn't just how things have always been; it's a relatively new trend, and trends can reverse.