6–8 May 2019, Washington State Convention Center, Seattle. The last fully in-person Build before the pandemic, and — looking back from 2026 — one of the most consequential keynotes Microsoft has given in the last decade. It didn't feel like a product show. It felt like Microsoft pulling a developer audience close and handing them a map of the next five years, with the unspoken instruction: here, hold on to this for a while.
We were watching very closely, because we were ten weeks old. ThreeB IT had been incorporated on 1 March 2019, and almost every strategic bet we'd just placed — stay on the Microsoft stack, build and run, take Windows and .NET seriously as a production platform — was about to be either confirmed or quietly contradicted on a stage in Seattle. It got confirmed. Comprehensively.
"Trust as a design principle"
Satya Nadella opened not with a feature but with a frame. The recurring word of the keynote wasn't "AI" or "cloud" — it was trust. His line that stuck with us was almost an engineering instruction rather than a slogan:
"Trust in everything that we build, in the technology we build, is so core." — Satya Nadella, Build 2019 keynote
He paired it with a sharper one — "privacy is a human right as much as it is an engineering design principle" — and the framing underneath both was the idea he'd been circling for a couple of years: that as computing dissolves into everything around us, the people who make platforms can't treat trust as a marketing afterthought. It has to live in the design process, next to the data model and the threat model.
For a two-month-old company deciding what kind of shop it wanted to be, that landed hard. We build for industries where a bug isn't a cosmetic regression — it's a missed export, a failed payment, a compliance finding. Hearing the CEO of the platform we'd bet on say, on stage, that trust belongs in the core design process rather than the press release was the permission slip we didn't know we were waiting for. It's a sentence we've quietly run a company on ever since.
Windows learned to love Linux — properly this time
The announcement that got the loudest, most genuine developer reaction was WSL 2: the Windows Subsystem for Linux, rebuilt on an actual Linux kernel shipped inside Windows for the first time, instead of the system-call translation layer that WSL 1 had used.
This was not a small detail dressed up as a big one. It was the other way around. WSL 1 was clever but leaky — anything that touched the kernel in an unusual way tended to break, which in practice meant Docker. WSL 2 fixed the foundation. Microsoft committed to shipping a real, open-source Linux kernel (4.19 to start), tuned for a lightweight utility VM, serviced through Windows Update. The performance numbers they put on screen were the kind you don't usually get to claim honestly:
- Up to 20× faster unpacking a zipped tarball, versus WSL 1.
- 2–5× faster for everyday developer operations —
git clone,npm install,cmake. - Native Docker — the real Linux build, finally running inside Windows because the system-call compatibility was finally complete.
For us this was the difference between Windows being a workstation you tolerated for Linux work and one you'd actually choose. Our whole pitch is "build on the Microsoft stack without giving anything up." WSL 2 deleted one of the last honest "but" clauses from that sentence.
A terminal you could actually use
Right alongside WSL 2 came Windows Terminal, and the room understood immediately why it mattered. For years the Windows console had been the embarrassing relative at the family dinner — functional, ancient, allergic to anything Unicode. The new Terminal was a clean break:
- Tabs, each connected to whatever you wanted — Command Prompt, PowerShell, an Ubuntu shell on WSL, a Raspberry Pi over SSH.
- A GPU-accelerated DirectWrite/DirectX text rendering engine that drew CJK characters, emoji, Powerline symbols, icons and programming ligatures without breaking a sweat.
- Settings in a structured text file, profiles, custom fonts, colours, transparency.
- Open source, on GitHub, console core and all.
The "open source, on GitHub" part is easy to skim past now and was genuinely a statement in 2019. The company that once treated its source like crown jewels was shipping its terminal — and its console — in the open and inviting pull requests. That posture, more than any single feature, told us the cultural shift inside Microsoft was real and not a conference slide.
The bet of the decade: one .NET
The same day, in a developer session and a blog post from program manager Richard Lander, Microsoft set out the move that everything we do today rests on: .NET 5. The plan was to take .NET Framework, .NET Core, Xamarin and Mono — four lineages that had drifted into a confusing tangle — and converge them into a single .NET platform, one runtime and one set of libraries, targeted for November 2020.
The naming alone told the story: they skipped ".NET Core 4" to avoid colliding with the Windows-only .NET Framework 4.x, and dropped the "Core" suffix entirely. The message was there is just one .NET going forward. One runtime everywhere — desktop, web, cloud, mobile — with uniform behaviour and a single developer experience.
We want to be precise about chronology, because it matters: the unified .NET 5 vision was set out around Build 2019 (the public blog post landed on 6 May 2019, the conference's opening day), and the platform itself shipped in November 2020. We're describing a roadmap announcement here, not a finished product handed out at the booth.
But that roadmap is, more than any other single decision, why ThreeB IT bet its technical future on this stack with a clear conscience. The fragmentation of the .NET world had been a real reason for caution. Watching Microsoft commit, publicly and with a date, to ending that fragmentation removed the largest objection we had to going all-in. Six years on, every product we ship runs on the platform that vision became.
Fluid, Edge, and an early glimpse of agents
Two more announcements are worth pulling out, one because it was strategically interesting and one because — in hindsight — it was a quiet preview of everything that would dominate Build seven years later.
Fluid Framework was Microsoft's attempt to blow up the document. Instead of a file being a monolith owned by one app, Fluid proposed a web-based, componentised document model: deconstruct content into collaborative building blocks, co-author them at high speed and scale, and recombine them across applications. Most striking in retrospect was the third pillar — Fluid explicitly made room for intelligent agents to work alongside humans, translating text, fetching content, suggesting edits and running compliance checks inside the document. Read that sentence again with 2026 eyes. The agent story Microsoft now builds entire conferences around had a recognisable ancestor on the Build 2019 stage.
Chromium-based Edge was previewed too — a rebuilt browser on the Chromium engine, with an Internet Explorer mode for legacy enterprise sites, Collections, and stronger privacy defaults. For those of us who maintain line-of-business apps that some customer somewhere still opens in IE, the IE-mode promise was less exciting and more deeply, practically reassuring.
Underneath all of it, Nadella kept hammering the platform-openness theme — ".NET and Java are first class, SQL and Postgres are first class" — and pitching Azure as "the world's computer." Open by default, multi-language, multi-database. That, too, matched the kind of company we wanted to build: close to Microsoft, but not boxed in by it.
Why it mattered for us
Here's the part that still feels slightly improbable when we say it out loud.
ThreeB IT had been a legal entity for about two months when this keynote went out. We had a plan written down, a stack chosen, and the ordinary low-grade anxiety of a brand-new company wondering whether it had bet on the right horse. And then, over three days in Seattle, the largest software company on earth got up and drew — in detail, with dates — the exact world we'd decided to build in.
One .NET. We'd committed to .NET; Microsoft committed to unifying it.
Windows that runs Linux without compromise. We wanted to build on Windows without apologising for it; WSL 2 removed the apology.
Trust as an engineering principle, not a press release. We'd chosen to serve industries where correctness is the whole job; Nadella put that value at the centre of the keynote.
Open by default — .NET and Java, SQL and Postgres, all first class. We wanted to stay close to one vendor without being trapped by it; Microsoft's openness made that a coherent position rather than a contradiction.
The strategic bets we'd made on 1 March 2019 got validated, on stage, ten weeks later. That's not why we made them — you don't found a company hoping a keynote will agree with you — but it's hard to overstate what it does for a young team's confidence to watch the platform owner independently arrive at your thesis. We didn't need the reassurance to keep going. We were very glad to have it anyway.
There's a through-line from that 2019 room to where we are now. We've been to every Build since 2012, and the ones that stay with you aren't the ones with the flashiest demo — they're the ones where the direction clicks into place. 2019 was one of those. WSL 2 and Windows Terminal made our daily work better the same year. .NET 5 became the foundation under every product we'd go on to ship, Xircuit and Outastory included. And the agent idea hiding inside Fluid Framework turned out to be the seed of the entire decade that followed.
Build 2019 didn't just preview some software. For a ten-week-old company in Ibbenbüren, it confirmed the map. We've been navigating by it ever since.
Sources & further reading
- Microsoft Command Line Blog — Announcing WSL 2: https://devblogs.microsoft.com/commandline/announcing-wsl-2/
- Microsoft Command Line Blog — Introducing Windows Terminal: https://devblogs.microsoft.com/commandline/introducing-windows-terminal/
- .NET Blog — Introducing .NET 5: https://devblogs.microsoft.com/dotnet/introducing-net-5/
- Visual Studio Magazine — Unified .NET 5 Unveiled: 'Just One .NET Going Forward': https://visualstudiomagazine.com/articles/2019/05/06/net-5.aspx
- OnMSFT — Build 2019: Microsoft announces Fluid Framework: https://onmsft.com/news/build-2019-microsoft-announces-fluid-framework-a-new-platform-for-shared-interactive-experiences-coming-later-this-year/
- GeekWire — Microsoft doubles down on trust and privacy as Satya Nadella opens Build: https://www.geekwire.com/2019/microsoft-doubles-trust-privacy-satya-nadella-opens-build-conference/
- diginomica — Build 2019 — Nadella pitches a crowd-pleasing 'holy trinity': https://diginomica.com/build-2019-nadella-pitches-crowd-pleasing-holy-trinity-stays-close-core-engineer-audience
- Windows Central — Top 5 announcements from Microsoft Build 2019: https://www.windowscentral.com/top-5-announcements-microsoft-build-2019
A note on chronology: the unified .NET 5 vision was published on 6 May 2019, the opening day of Build, and the platform itself shipped in November 2020 — we describe it here as the roadmap announcement it was. Performance figures for WSL 2 are Microsoft's own published benchmarks from the announcement.
Image credits
All photos are used under their respective Creative Commons licences; we are grateful to the photographers.
- Seattle 3 — © Daniel Schwen, CC BY-SA 4.0, via Wikimedia Commons (source).
- Arch Linux system update via pacman on an Acer laptop — © Solijon Solayev, CC BY-SA 4.0, via Wikimedia Commons (source).
- Important whiteboard diagram - save! — © pepperlime, CC BY-SA 2.0, via Flickr (source).