I'd say only positively.

Regarding the article, this statement really freaked me out:

> So, we’ve got an idea - why can’t we place such a server in front of our application and make it cache content for all users in the world?

Seriously? They'd never even _heard_ of gateway / reverse proxy caching? They came up with it independently? I knew HTTP caching wasn't understood very well but this shows that it's so much worse than I imagined.

It's sad that such a fundamental aspect of the web's architecture is just completely off the radar for so many "web developers". That's not a knock on the Scribd folks, it's a systemic problem across our entire industry as far as I can tell.