That line I quoted acknowledges that the problem was overpromising and underdelivering, but doesn't (that I can see) acknowledge that the solution is specifical

That line I quoted acknowledges that the problem was overpromising and underdelivering, but doesn't (that I can see) acknowledge that the solution is specifically to promise less rather than deliver more. In particular the word "fast" there is a little worrisome to me. > The reason that threads & spaces are taking a while to ship in EX is literally because we have slowed down, and made sure everything is fully working before we ship it. But you already did ship it. And my perception is that what you're doing now is again rushing to catch up with the overpromises. My question is what are you going to do going forward to make sure that things that aren't ready never ship in the first place --- and that there are no more blog posts or the like about how amazing the next thing is (whatever that may be) until it has everything it actually needs to be amazing. Anything that has to do with fixing what you already shipped is still on the delivery side. My question is about what are the processes on the promise side to ensure that unrealistic promises are not made in the first place. I appreciate your engaging with me here and I want you to know that I appreciate what Matrix is trying to be. I'm still using Matrix in the same limited way I've been using it for a few years now. I'd love to be able to use it for more purposes. But there is no amount of fixes to already-released things that can ever convince me to do that. The only thing that will convince me is when the "next thing" (or next several things, really) that rolls out is actually everything it was cracked up to be, instead of having major problems that require damage control after it's been hyped up as a groundbreaking step forward.