Yes. I’m not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).

Nominally, a decent bug report should have:

• the steps that got you the bug
• whether you can reproduce the bug
• what you expected to happen instead of the bug

Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!

Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.

It’s exactly this. The policies put in place by “healthcare administrators” (MBAs and such with healthcare flavoring, not people that actually know how to care for people’s health like doctors and nurses) are designed to process the most patience in the least amount of face time possible, so that each doctor and nurse can see more patients per day, meaning more office visit fees, meaning higher profit. My dad calls it the “cattle shoot” and I feel that’s a pretty apt analogy. It’s the same general reason that fast food restaurants and pharmacies and department stores are perpetually understaffed: fewer staff members means lower “overhead” costs.

This is called “Embrace, Extend, Extinguish”. Microsoft coined the term internally for their responses to open standards in the 90’s and 00’s.

https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

Misread, but I’m leaving it!

“May you live in interesting times.”

Did this ever get better than the initial reviews? It seemed mediocre-to-bad. Steam still calls recent reviews “mixed”.

Lots of discussion here of Zed being macOS-only. Multiplatform support is being tracked in this issue for Linux, Windows, and web:

https://github.com/zed-industries/zed/issues/5391