What a weird, sad, pointless article. There's nothing new about "platform engineering" or "internal developer platforms". The only myth is that these labels rep

What a weird, sad, pointless article. There's nothing new about "platform engineering" or "internal developer platforms". The only myth is that these labels represent new ideas or unique approaches. These are just not-particularly-new names for something software companies and IT organizations have been doing for decades. And GCP offers no particularly unique or innovative tools, services, or support for building an internal platform. I used the exact phrase "internal development platform" for the automation infrastructure I was developing to provide resources, security, libraries, databases, web endpoints, etc for internal ASP.NET applications at a state university where I worked over 20 years ago. It ran on a half-dozen bare-metal physical servers in the datacenter across the hall from my office. And I knew at the time that we didn't come up with some brilliant new breakthrough idea for organizing application development, because the university's mainframe programmers on the other side of the building had built a similar automation platform over 20 years before that. We modeled a lot of our design on theirs. And here I am in 2024, working for companies, building exactly the same sorts of solutions, with all the same parameters and components, just in a different computing environment. Templates, access, runtime, database, storage, sessions, load balancing, logging, security. Whether it's a mainframe in the 80s, a few Windows servers in the 00s, cloud VMs in the 10s, or Kubernetes in the 20s, it's all the same problem space, and guess what, Google or anyone else preaching "platform engineering" hasn't created or realized anything new.