Om Malik, 1966–2026: The Pre-Obituary Was Real

What happened

Om Malik has died. John Gruber confirmed it Friday morning at Daring Fireball, linking back to the post Malik himself published 36 hours earlier — a piece titled '1966–2026' that read like an obituary because it was one. Malik wrote it while he could still write. The 226-point Hacker News thread that hit #1 on Thursday wasn't a meditation on mortality; it was a heads-up.

Malik founded GigaOm in 2006 after a stint at Business 2.0 and Forbes. At its peak the site employed roughly 70 people across beats that no general-interest tech publication covered with the same depth: cloud infrastructure, semiconductors, broadband economics, mobile carriers, the unsexy capex underneath the consumer internet. GigaOm Research — the paywalled analyst arm — was an early attempt to turn blogging into a Gartner-style business, and it nearly worked. The company shut down operations in 2015 and was acquired out of receivership; the brand survived, the original editorial DNA did not.

Malik himself stepped back from full-time writing after a 2011 heart attack at 41 and moved into venture capital at True Ventures, where he stayed for the rest of his career. His personal blog at om.co kept publishing — photography, short essays on technology and aging, the occasional sharp piece on a deal nobody else had seen yet.

Why it matters

If you're a developer in your thirties or forties, there's a non-trivial chance your intuitions about how the industry actually works — how AWS pricing relates to fiber buildouts, why Cisco's gross margin matters, what 'the cloud' meant before it meant Kubernetes — were shaped by GigaOm beat reporters Malik hired and trained. Stacey Higginbotham on broadband. Derrick Harris on Hadoop. Barb Darrow on the enterprise stack. That bench produced the connective tissue between vendor announcements and what they meant for the people who had to actually deploy the things.

That job barely exists now. The trade press that covers infrastructure for working engineers has thinned to a handful of independent newsletters, a couple of analyst shops, and whatever vendors are willing to publish on their own blogs. Substack absorbed some of it. Most of it just left. The substitution isn't 'the same content in a new format' — it's a smaller total volume of original reporting, distributed across fewer reporters who answer to fewer editors.

The community reaction on Hacker News tracked this. The top comments weren't sentimental; they were specific. People named the post that made them subscribe to GigaOm Pro in 2009. They quoted Malik's 2008 piece on Cisco's UCS launch. One commenter — a former AWS PM — said GigaOm's coverage of EC2 reserved-instance pricing in 2011 was the first analysis he'd seen that actually understood the unit economics. That's the thing that got lost: not the inches of copy, but the small number of people whose phone the SVP of Networking would actually pick up.

Gruber's tribute itself is worth reading on its own terms. Daring Fireball has been writing about the same beat for 24 years, and Gruber's relationship with Malik went back to the early TypePad era. The post is short, sharp, and refuses the temptation to make Malik's death about the industry — which is, of course, why everyone in the industry is sharing it.

What this means for your stack

Nothing about your stack changes today. Your Postgres still runs. Your CI still flakes. The point is upstream: the information environment you use to make stack decisions has been getting worse for a decade, and one of the few remaining people who built the better version is gone.

The practical move, if you read this and feel something, is to pay for the independent infrastructure writers who are still doing the work. Pragmatic Engineer. The Pragmatic Programmer. LastWeekInAWS. Bytebase's database newsletter. CockroachDB and Neon's engineering blogs when they're being honest. There are maybe two dozen working tech journalists left who can read a press release and tell you what it actually means for your capacity plan, and most of them are one Stripe subscription away from quitting. Subscribe to one this week. Pick a different one next quarter.

The second move is to write more yourself. Malik's career was a forcing function for the proposition that engineers who can write clearly about what they're seeing have leverage the trade press can't replicate. om.co was a personal blog that out-reported newsrooms with budgets. The pattern still works; the supply is just thinner now.

Looking ahead

The tech press cycle Malik helped invent — daily blog → analyst arm → conference business → venture fund — has been disassembled and reassembled as podcasts, newsletters, and Twitter accounts. The economics are mostly worse and the reach is mostly narrower, but the form is durable. Someone is going to rebuild GigaOm. They probably won't call it that, and they probably won't make it to 70 employees. But the gap Malik leaves is the kind of gap that gets filled, eventually, by somebody who reads his old posts and decides they can do it too. If that someone is you, the archive at gigaom.com is still up. Start there.