> Letting any of these secondary runtimes develop a significant base of applications in the store risks putting Apple in a position where the company that cont

> Letting any of these secondary runtimes develop a significant base of applications in the store risks putting Apple in a position where the company that controls that runtime can cause delays in Apple’s release schedule, or worse, demand specific engineering decisions from Apple, under the threat of withholding the information necessary to keep their runtime working. Boy does that bring back memories, from the late 1980s, of various Microsoft products running on MacOS. Apple had to bend over backwards to make API improvements, while not breaking Excel (and others). IIRC, there were various kludges that Apple finally removed, causing much distress to the average user. This wasn't about frameworks per se, but it was about the MacOS toolbox during the 6.x and 7.x era.