The problem with this article (other than the usual SM lack of substance) is that almost all the examples are portfolio sites for artists and designers. How about showing these principles applied to more complex projects - applications, e-commerce sites, corporate sites, admin systems, etc?
This is the problem with most SM articles and with most web design sites in general. I say this as someone who is featured in this post. Portfolio sites have a perfect reason to be minimal: the work comes first.
But that's what you get from an article that takes an aesthetic and works backwards — the exact opposite of a good design process.
Web design is basically communications design, on the Internet; it doesn't involve functional aspects (just reading, and finding/clicking links to enable more reading.) When you're designing a web app—industrial design, on the Internet—you're just doing UI design, and a good UI book will help you more than anything with "web" in the title.
I like this part: "Subtract Until It Breaks". It's easy to put stuff on a page or in an app because someone might need it, but when you start really limiting yourself it forces you to put it (be it a button or some text, whatever) where it's most intuitive, not just blast it all over the site.