Yeah… An example, persistence was announced more than 3 years ago and has been “shuffled around” numerous times for something that should objectively take a few months to plan, implement, test, and release. Heck, this was a year ago now
[VRChat Request] Regarding local persistence · Issue #567 · vrcx-team/VRCX · GitHub
where persistence was “maybe” 1.5-3 months out. The update on that post from last October the answer was the same as now too with things being shuffled around. I really hope that internal planning is largely about how to plan to not shuffle things.