4 ms·
I remember when the issue tracker for TypeScript or VSCode was still relatively new, the issue quality was much better. Now if you look at their issues, it's li
by Ciantic 6y ago
I remember when the issue tracker for TypeScript or VSCode was still relatively new, the issue quality was much better. Now if you look at their issues, it's like trying to wade through spam, I hope they have specialized people who don't get demoralized from reading the issue list.
For example just one issue last hour "Slow performance" and basically list of extensions, OS info. To track that one down, they should test each and every extension listed, and still might not have a good understanding what is going on.
- aloisdg 6y agoI would close the issue because the OP didnt search enough. A MCVE should be provided with steps to reproduce. OP should do the work of testing each extensions one by one
- Cthulhu_ 6y agoThe bigger your OS project gets, the more you have a need for help curating and triaging issues; you need a team of customer support, basically. And patience. So much patience.