Hardly. Why do you say that? I have personally worked on bugs reported by end users.
That's been my experience. Bugs reported and then either ignored or closed as duplicates of ancient bugs. See https://tommorris.org/posts/9491 (not my post, but similar experience).
Half of the problems listed are about how the app doesn't provide macOS-specific integrations. The rest are very minor usability issues that might have valid justifications for being that way. I am not inclined to view these as being terribly legitimate complaints.
As an excel developer in the 90's, this brings up great memories. I wrote the Doom Excel credits in Office 95. I wish I'd had thought of doing this instead. Kudos.
Do you think there's anyway that something like that could be shipped by Microsoft these days?
A dev on my team wrote the following Excel 2000 credits (it was a flying carpet-like game). Afaik that was around the time BillG put his foot down and mandated no new credits. Enterprise customers felt these credits were both a sign of wasted engineering time ("you could have fixed x bugs instead!" and wasted disk space. It's logical, but only partly true. Shipping software on CD means a very long stabilization phase. You couldn't really "fix more bugs" because every bug fix had a risk of introducing another one. That means some Office teams would literally complete their work a year before shipping. They'd sit around half-heartedly helping other teams. That's when someone would take time to write credits. These credits were often tightly-optimized C and assembly, taking very little space. The facts couldn't overcome the optics, so that was the end of fun Microsoft credits.
Hardly. Why do you say that? I have personally worked on bugs reported by end users.
That's been my experience. Bugs reported and then either ignored or closed as duplicates of ancient bugs. See https://tommorris.org/posts/9491 (not my post, but similar experience).