Rubs me the wrong way when these same companies can just re implement the API and cause massive hurt to an open source competitor.
What do you propose in that scenario. Copyrighting api has never been a thing prior and likely wont be as soon as the whole affair is appealed yet again.
Why should you be able to control who makes a compatible part? Do you want your car company maximizing revenue by not allowing you to buy anything but new parts of their manufacture installed by their techs? Lets do it one better fueled by gas bought at a station willing to give the manufacturer a kickback. Perhaps to license the design of the pump connection.
This future is so fundamentally broken and stupid we would do better to abolish all forms of intellectual property rather than fall into this moronic trap.
DRM for machinery is absolutely already a thing.
What about shifting open source licenses so that duplicating an open source API in a proprietary product, or using a product that does so, is a violation of the license agreement?
Correct. But Redis Labs very visibly and substantially funds development of the BSD-licensed Redis core database.
Some of "open source hosting" companies did the same. I always think of Heroku hiring Matz, as an example.
Customers are paying them to maintain and operate the hosted version of these projects. That’s valuable in itself and should not be seen as stealing money from the software’s authors.