But Arjun knew.
Tonight, something was wrong.
He dove into the EPPlus source code on GitHub. There it was: ExcelPackage.Load(stream) deserialized every XML part inside the .xlsx zip archive. Every shared string. Every drawing. Every fragile reference. The library was brilliant, faithful to the Open XML spec—but it treated every load like a cathedral restoration. epplus
He’d written this C# console app three years ago. Back then, it was a scrappy script using EPPlus 4.5, just to save his team two hours of manual copying and pasting. Now, the system had metastasized. It pulled from three APIs, two SQL databases, and a CSV vomited out by a legacy mainframe in the basement. But Arjun knew
EPPlus, like all great libraries, had taught him a deeper lesson: EPPlus abstracts away the horror of Open XML’s SharedStringTable and CellValue types, but it cannot abstract away memory. The “deep story” isn’t about Excel—it’s about the gap between what we ask computers to hold and what they can actually hold. There it was: ExcelPackage
He added a comment to the new codebase, right above the using statement:
