Don't recommend memoizing selectors (#1707)

As per the discussions below, memoizing selectors does not improve performance
significantly as of v4. Thus we should avoid recommending selector memoization.
Note that the same paragraph was removed from the README in PR #550
(pmndrs/zustand#550)
and this section may have been left behind as an oversight.

- pmndrs/zustand#658
- pmndrs/zustand#971

Author: galaxydevman

docs/recipes/recipes.mdx

@@ -65,29 +65,6 @@ const currentBear = useCredentialsStore((state) => state.currentBear)
 const bear = useBearStore((state) => state.bears[currentBear])
 ```
 
-## Memoizing selectors
-
-It is generally recommended to memoize selectors with `useCallback`.
-This will prevent unnecessary computations each render.
-It also allows React to optimize performance in concurrent mode.
-
-```jsx
-const fruit = useStore(useCallback((state) => state.fruits[id], [id]))
-```
-
-If a selector doesn't depend on scope,
-you can define it outside the render function
-to obtain a fixed reference without `useCallback`.
-
-```jsx
-const selector = (state) => state.berries
-
-function Component() {
-  const berries = useStore(selector)
-  // ...
-}
-```
-
 ## Overwriting state
 
 The `set` function has a second argument, `false` by default.