Apologies for commenting on a closed thread but some things need to be said not so much for the OP but for all of us to think cause I see this logical fallacy often and will like to present some things as a systems architect and software programmer/engineer.
When we have guests in our house and we cook for them, what is one of the first questions we ask? Do you like it? or is there anything missing? or at least you expect a comment, not to praise but to at least know that everything is ok. Common sense. We actually do that in most human interactions. Is the car you bought good? Is the PC fast? Is this phone any good? Is the thread I made in this forum useful? etc...etc...
In a similar way, in software case, a developer also needs to know if the software they made is working and functions in a decent way at least, or if the changes, additions, and modifications they do over each version, functions satisfactorily and properly or what kind of impact they have on the software and the system. They cant test EVERY PC and EVERY combo of software and hardware to know ahead of time. We know often that something that works for us, doesn't work for others and vice versa. A change may perform well on AMD, not on Intel, or the other way around. Some things work under some conditions but not under other conditions.
So... here is the tricky part... How do you expect a developer and programmer to know????? Guess and become oracles??? Smoke a joint??? Look in the magic ball?? No... There are 2 ways.
* Use telemetry (which is so misunderstood) to measure the impact of their changes. For example, telemetry software, monitors the startup time with the xxx option enabled or disabled, and collects those statistical data that will show them for example that out of the 100.000 users that enabled a feature, 90.000 run the software faster and that means the change works properly. If they add telemetry tho most of you will riot against the evil empire that spies on you.
* Politely ask the user for feedback: Hey does that thing we did works for you??? Do you see any impact??? Let us know so we can make this better.
And we complain about both. Think about it for a second... From one side you want the software to improve not just in function but in performance too, on the other hand, you don't want to tell the developer if a modification they did is indeed working and so, how are they going to make things better when they don't really know how a change is impacting users?
We cant have all the cake and eat it too.
Just food for thought...