[Suggestion]: How to avoid null checks when initializing useRef later

Summary

The example is very bad.

Page

https://react.dev/reference/react/useRef#avoiding-recreating-the-ref-contents

Details

The solution how to avoid this pitfall doesn't seem very robust. If for any reason you wanted to instantiate to VideoPlayer but you want your ref to generally be of type VideoPlayer | null you will never be able to put a null in there.

A more robust way actually seems to leverage useState via:

const [playerRef] = useState(()=>({current:new VideoPlayer()}))

While investigating this issue i've concluded that people in general misunderstand what useRef is, going to the extremes of thinking it's "just for dom elements". playerRef in this snipper is exactly MutableRefObject<VideoPlayer> and this approach doesn't involve all kinds of acrobatics, like lying to a type checker, checks inside the render body etc.

閱讀連結的「avoiding recreating the ref contents」部分中的 useRef 文件，並檢視目前的範例及其中所述的型別假設。將提議的 useState 方法與現有指引進行比較，然後更新範例或說明，以釐清預期的 ref 型別、null 行為以及初始化方面的取捨。