If WASM+WASI existed in 2008, we wouldn't have needed to created Docker. That's how important it is. Webassembly on the server is the future of computing. A standardized system interface was the missing link. Let's hope WASI is up to the task!
Your CI/CD pipeline should start on the developer's laptop. If it only starts after a git push, you're slowing your team down and throwing money down the drain.
CI/CD "shift left" is the lowest-hanging fruit for engineering efficiency in teams of 20+ engineers IMO.
Docker's philosophy in a nutshell:
1) solve a painful problem with a simple tool. Ignore the purists criticizing the tech
2) get lots of happy users
3) gradually improve the tech without sacrificing simplicity
4) tech previously reserved for purists is now democratized
5) repeat
After a long break (and 2 babies), I’m working on something new. Before I tell you what it is, I want to talk about who I’m building it with. Meet my co-founders, @sam_alba and @aluzzardi. 10 years ago we left France for Silicon Valley, complete outsiders. The result was Docker.
Anthropic pushes MCP. Google rushes A2A. Welcome to the AI Standard Wars.
"But they are complementary! Each standard has a purpose"
Oh my sweet summer child. This is war.
Fun fact: "docker" was an internal project codename. I thought it was a silly name and that we should change it before launch. Thankfully we launched early by accident - too late to change. Later we renamed the whole company to Docker.
Here's why we did it:
1. A compiled binary that didn't require installing a language runtime and therefore didn't trigger tribalism. Devops teams back then were fragmented across Python, Ruby and Java. Every tool written in one language would instantly get cloned in the others.
Here's why we did it:
1. A compiled binary that didn't require installing a language runtime and therefore didn't trigger tribalism. Devops teams back then were fragmented across Python, Ruby and Java. Every tool written in one language would instantly get cloned in the others.
