Everyone is gawking over the M1 > because your app is using their "IP" in the form of all the libraries and tooling they nigh unto force you to use to build ap

Everyone is gawking over the M1 > because your app is using their "IP" in the form of all the libraries and tooling they nigh unto force you to use to build apps that run on their phone; like, to them, UIKit (I presume), Metal (which many people are only using because Apple refused to implement OpenGL or Vulcan), and (this is rich) apparently even Xcode And say what you will about Xcode, but I’m literally building in Vapor 4 (server side Swift) with all of its warts because I experience trauma leaving Xcode. JetBrains and VSCode are painful to get to function like Xcode - but if there are any pointers to make it a better experience I’m al ears... Edit: just to reiterate. Users want long battery life, fast compile times / snappy apps, better connectivity into life... And honestly Apple has almost screwed itself executing perfectly on those demands in its native platform. We forget at the end of the day we all (devs, manufacturers, etc) are working to bring value to a customer, who has other relationships with other suppliers. Those other relationships create multiple Pareto equilibriums based on the utility function of the customer... this case is trying to reweight (with more philosophical reason) how millions of customers have previously and consistently chosen to balance their decisions