How has the adoption of cloud IDEs affected Docker's usage and what are some insights on the intersection between cloud-based development and Docker?

I’ll start with the customer problem, which is that these apps are complex. Ninety nine percent of our customers are deploying the containers produced by their developers using Docker to Kubernetes. These are not just one or two containers but tens of containers, 20s, 30s of containers. It’s become a huge challenge to give developers an experience where they can locally iterate, write code, and build because replicating that 20 or 30 container stack locally is just too much for the machine.

Even with Apple pouring hundreds of cores into their M1s and M2s—which is another reason why there's still a lot of gravity on local-only dev—what we're actually seeing is many companies say, "We're going all in the cloud because the clusters are up in the cloud.”

The leading trend is a hybrid mode where developers are working locally on their container but through the magic of networking, they, being a team, are working in a shared dev cluster. 

At the center of that cluster is a dev staging version of their Kubernetes application, so the 20 or 30 containers are running in that shared cloud environment. That’s based on customer feedback, explorations, and just listening to people in the community.

We believe that that's going to be the mainstream way that this market transitions. 

There will be local development going on simultaneous with it being tethered to a shared dev environment in the cloud. That's how you're going to give dev that local feedback loop, that local performance, and the benefit of shared resources in the cloud which is very difficult today unless you're all up in the cloud. 

That’s really hard today, particularly when it comes to customizing your tooling and having that same freedom you have locally, but we're behind this trend, and you’ll see more from us on this in the coming year.