>but now browsers and operating systems are so secure that it's mostly a non-issue Right, which is the point - it took an absolutely behemoth effort backed by

>but now browsers and operating systems are so secure that it's mostly a non-issue Right, which is the point - it took an absolutely behemoth effort backed by megacorps to get us to this point. These applications are public-facing because that's the key way for the corps to make money - content delivery. Why would anyone put this same effort into building more complicated internal services enabling derivative services to extract value from their platform? > Calculating how much computing resources you're using is something that i.e. AWS Lambda does already Yes, exactly - another megacorp built a service that makes them huge amounts of money, and now they sell access to it. This code is certainly not publicly accessible So, again, help me bridge this gap - what possible reason would Spotify (to further GP's example) build such a platform for? This means that Spotify needs to maintain massively more infrastructure in order to help others extract value from their platform. It just doesn't check out. Is it objectively a more efficient method of computation? Yes. Is it also completely misaligned with corporate incentives in the modern day? In my opinion, yes.