(I wrote SumatraPDF).
I agree that Adobe has more features than SumatraPDF.
Not necessarily the PDF spec itself - SumatraPDF displays pretty much any PDF you throw at it, just way more options and stuff.
And it's not exactly slow. I'm sure the core rendering of PDF pages is same or faster.
It's just slow to start. Like very, very, sluggish slow. And it's very visible to users.
I don't think it's the features that cause the slow startup. They just don't seem to care about optimizing it.
Chrome has more features that Adobe Reader. It has video calling, a capable PDF viewer and all the other stuff in ever growing web standards.
And yet it starts up fast. Not instant as SumatraPDF but way, way faster than Adobe Reader.
I think that it's more than fair benchmark regarding complexity of the app.
The difference is that Chrome team cares about performance, including startup speed, and they spend a lot of resources on it.
I remember Chrome was counting and removing C++ static initializers from their code (the code that runs before main()) because that contributes to startup speed.
That's the level of care you need to have and I think Adobe just doesn't have it.