From e2a63bbf6bc818d0c3a505c2b149baccac20bde1 Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Wed, 28 Mar 2018 15:13:28 +0100 Subject: [PATCH] 20,000 => 50,000 --- content/docs/design-principles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/design-principles.md b/content/docs/design-principles.md index c6db0209..e0f61a34 100644 --- a/content/docs/design-principles.md +++ b/content/docs/design-principles.md @@ -43,7 +43,7 @@ If we want to deprecate a pattern that we don't like, it is our responsibility t ### Stability -We value API stability. At Facebook, we have more than 20 thousand components using React. Many other companies, including [Twitter](https://twitter.com/) and [Airbnb](https://www.airbnb.com/), are also heavy users of React. This is why we are usually reluctant to change public APIs or behavior. +We value API stability. At Facebook, we have more than 50 thousand components using React. Many other companies, including [Twitter](https://twitter.com/) and [Airbnb](https://www.airbnb.com/), are also heavy users of React. This is why we are usually reluctant to change public APIs or behavior. However we think stability in the sense of "nothing changes" is overrated. It quickly turns into stagnation. Instead, we prefer the stability in the sense of "It is heavily used in production, and when something changes, there is a clear (and preferably automated) migration path."