All that was solving a (local) infrastructure problem. Cloud moved the infra to someone else's data center but it did not take long before they started allowing anyone to consume the back end services as a platform. (My pet theory is that S3 is the most industry-changing software written in the last 30 years...)
Today, people are locked into the platform. I can't move from X to Y because my business is welded to AWS S3, Lambda or Azure Kubernetes or whatever.
And, yes, there were hopes for portability early on even though it was clear that the cloud providers weren't much interested and it became harder as services became more complex. There are some glimmers of portability--such as using my former employer's OpenShift for Kubernetes--but single-pane-of-glass management and API translations between cloud providers never really panned out.
> But. And here's where the comparison to cloud comes in; the details of that evolution seem a bit fuzzy.
Maybe I have rose-tinted glasses on, but cloud computing was never "fuzzy" the way LLMs are. Cloud offerings were (and even moreso now, are) platforms. At the time the concept of a technical platform was very well understood with plenty of prior art. .NET is an example that leaps to mind. The trade-off was you give up control and submit to vendor lock-in, but the platform abstracts away small details so you can focus on your business. In short, cloud wasn't a huge leap, conceptually.
With LLMs, conversely, there isn't really much you can point to and say "this is a natural progression of ____". It's an entirely new thing, with entirely new problems.