This thread was brought up on another site. I had forgotten about it, but I think the first post in particular is worth reading for anyone who never saw it or for those who also forgot.
No, it does NOT have anything to do with the very hard to understand delay in a status update. That is a whole 'nother matter and one that WT needs to get out of the way. After all, it's a week since we were told "Saturday night after 9:00 PM". I'm pretty sure no one can imagine what could happen to explain such a delay!
But this thread had to do with the simple fact that a lot of people who aren't lucky enough to get into Treg not being able to even imagine why it wasn't in GR release when this thread started. Which is also perfectly understandable. But in the case of GR, once you had one, learned a lot more about it, etc, there was a pretty consistent view of Treg members that the delays in GR were understandable. Who knows, maybe when we get the status update, the delay in that for the past year will be understandable even though I can't imagine how at the moment.
Of course, a lot of changes have come since this thread started as this came less than a year after the first Treg units were shipped out. Back then there were lots of problems and it was pretty clear to Treggers that shipping it to the general customer would not have been a good idea.
But what about when more problems were solved? In some cases it is easy to have very limited information about the number and degree of problems and still say it isn't ready to ship. By that I mean if I only have enough info to know the number of problems is 50-1000, then because 50 is too many, it doesn't matter if it may be a lot more. But what happens if the limited information means I only know the problems may range from 2-50? Well, 2 would be fine, but since it may also be as high as 50, I simply wouldn't be able to say it is ready to ship without a lot more information.
However, moving to more recent events, the situation has changed again. WT mentioned that the last firmware (before the fork) was good enough for shipping, so that is no longer a question. That version came out in Sept 2018. We don't know at what point they decided it was good enough though. So, does that mean they should be shipping by now?
Well, we have the answer to that too, even if some don't think it is the best decision. The question to me is whether it is an understandable or reasonable one, even if personally some don't like it.
The answer was the lack of available memory to handle problems that would inevitably come up with GR and to provide customer support (these almost certainly overlap). They also said it was for future improvements, but I think that is secondary to the others.
Customer support will be worse if they can't fix new issues quickly. How quickly things can be fixed are affected by two key things their present decision deals with. One is that any problem requiring rewriting some code has to first rewrite other code every time just to make room. That process not only takes a lot more time, but the rewriting of other bits of code greatly increases the chance of creating a new problem! Second, doing this fixing of old code while also rewriting the new fork means less time is available for both, thus both take longer. Third, and this is just a guess as WT hasn't specified anything I can recall, they may need the room to include new code which directly deals with supporting customers. They could have new, built-in, testing of things that go beyond what Treg testers have now (we can create logs to sent to WT which tells them more than just the characters we typed - I think they can tell things about timing and exactly how we struck the keys). Obviously the more info a customer can provide to WT, the easier it will be to fix any problem.
I suspect many will still just say they want it as is. That's fine. My point is just to show that there are understandable reasons for not doing so yet. That's as far as I can go without knowing more.
All of which is quite different than STILL not have a darn good status update - or even a poor one!