The minimalism worth having

There's a fundamental difference between removing what bothers you and removing what's unnecessary. The first is pragmatism; the second, judgment.

Apple has been making this distinction for decades. When Jobs removed the optical drive from the MacBook Air, it wasn't because it was hard to implement. He did it because most users no longer needed it, even though nobody had asked for it to be removed yet.

In software, we call many things minimalism that are really laziness or lack of judgment disguised as a decision. A form with five fields instead of fifteen isn't minimalism if the five are the wrong ones. A component with no styles isn't minimal, it's incomplete.

The difference is intention. Real minimalism has costs: the time it takes to decide what to leave out, the courage to defend what you removed, the ability to explain why what remains is enough.

When I design something, I ask: what happens if I remove this? If the answer is "nothing important," I already know what I need to do.

The minimalism worth having isn't the easiest to implement. It's the hardest to defend.