I understand the frustration.
It might help to understand that in nowadays world, a company doesn’t put a hardware product on the market without a huge amounts of logistics, with many people involved. So you have to fix a date, and as it is very hard to cancel it you have to make what you can to release at that time.
The other aspect is that it is near impossible to test everything on a hardware unit.
Each tester, each user has its own workflow, even a mechanical automaton is programmed with one particular workflow in mind.
A million users with each their own way to use the machine is hard to beat.
Last thing is that this is a brand new architecture, with most likely new devs.
So many aspects to debunk, that you might not have to retry in details if it’s the fifth version of the architecture you put out.
So yeah, nowadays I think it’s best, if you don’t want to deal with teething troubles, to wait a few months for the firmware updates to come out.
But if you are willing to try it anyway, cause you think it is still a nice box despite the present flaws, you might want to think that you are actually helping the community when you declare a bug. Cause you do.