>Sure, lets pipe user feedback directly into GitHub issues. Good luck with that if you have a hundred issues a day.
Average user is less than poorly educated about technology. Their level of competence when raising a bug is simply pathetic, a lot of times. I manage an email server for a family, they write to me "email doesn't work", I check issue and respond "domain should be gmail.com not gmail,com" (notice the comma).
This reminded me how sqlite team was getting emails or calls at night, from some random people because another software was crashing. User went to "about/legal" and found license of SQLite, so obviously they decided to contact SQLite and complain on bad software. https://github.com/mackyle/sqlite/blob/3cf493d/src/os.h#L52-...
Now imagine facebook api breaks backwards compatibility, so you get 1000 of new issues in a day with title "broken", "doesn't work", "shit is crahing so gave 1* fix it now I might review it later".
Average user is less than poorly educated about technology. Their level of competence when raising a bug is simply pathetic, a lot of times. I manage an email server for a family, they write to me "email doesn't work", I check issue and respond "domain should be gmail.com not gmail,com" (notice the comma).
This reminded me how sqlite team was getting emails or calls at night, from some random people because another software was crashing. User went to "about/legal" and found license of SQLite, so obviously they decided to contact SQLite and complain on bad software. https://github.com/mackyle/sqlite/blob/3cf493d/src/os.h#L52-...
Now imagine facebook api breaks backwards compatibility, so you get 1000 of new issues in a day with title "broken", "doesn't work", "shit is crahing so gave 1* fix it now I might review it later".