> What's the harm here if the APIs are temporary The “if” is carrying a lot of weight. It gives Microsoft a solid competitive edge and a form of vendor lock-i

> What's the harm here if the APIs are temporary The “if” is carrying a lot of weight. It gives Microsoft a solid competitive edge and a form of vendor lock-in in their otherwise mostly open product. We don’t know that they’ll be temporary forever. > They've stated the purpose of these "proposed APIs" Just like how they said recall would not be a required feature, but is a dependency of the file explorer in the next version of windows? Microsoft will say whatever looks good for them, obviously. > last decade But we do from the last 11+ years ;) I’d always err on the side of not trusting giant monopolistic corporations with a history of garnering good will to cash in on it later. Especially when that company has been very aggressively inserting itself in nearly every JS projects dependency/software delivery pipelines. I gain nothing by trusting them, but I stand to lose my project’s independence from them.