Zed adoption blockers #28970
Unanswered
EmilCataranciuc
asked this question in
General Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
Is there any effort being put into researching and tracking of any issues, discussions or other relevant documents preventing wider adoption of Zed? For example, in issue #15098 users mention that the issue is preventing them from adopting the editor full time. I am basically looking for a list containing such references. Preferably the list should be a combination of roadmap and issue + discussion based priorities. Would project maintainers be interested in such a list?
Thank you!
Edit:
Adding the list off issues and discussions matching the criteria mentioned above. The list is a work in progress.
Deal breakers on the Roadmap:
"Debugging": #13433
"Language-Specific Initiatives": https://github.com/zed-industries/zed/issues?q=is:issue%20state:open%20label:language
Arguably crashes, freezes and accessibility issues might be major blockers:[core label]
Editor or OS - freezing / hanging / locking
Improvement related to color contrast, screen reader support, keyboard navigation, etc
Crash issues: https://github.com/zed-industries/zed/issues?q=type:%22Crash%22 & crash
Freeze issues: freeze
Accessibility issues: accessibility
Issues & Discussions:
#5065 ~ 5 comment, 204 reactions Already a deal breaker in the Roadmap
#6756 ~ 6 comments, 130 reactions. Many comments seem to be leaning in the anti AI category. Might be worthy of a discussion among the team for strategy and vision adjustment.
#5120 & #8169 ~ 1 comment, 73 reactions, 1 PR
#15098 & #19103 & #16336 ~ 6 comments & 57 reactions
#4726 ~ 2 comments, 28 reactions
#24228 ~ 1 comment & 16 reactions
#4848 ~ 2 comments, 16 reactions
#4948 ~ 5 comments, 14 reactions, 1 PR
#8854 - no specific mention of it being an adoption blocker but might be implicit
#7680 ~ 1 comment, 1 reaction
#7621 ~ 1 comment
#6722 - no specific mention of it being an adoption blocker but might be implicit
#6424 ~ 1 comment
#4322 - no specific mention of it being an adoption blocker but might be implicit
#4663 ~ 2 comments
#4687 ~ 1 comment
#4836 - no specific mention of it being an adoption blocker but might be implicit
#20159 ~ 1 vague comment
#20117 & #13116 - no specific mention of it being an adoption blocker but might be implicit
Accessibility:
#8503 - no specific mention of it being an adoption blocker but might be implicit and relevant to accessibility.
#6817 - no specific mention of it being an adoption blocker but might be implicit and relevant to accessibility.
UX:
#4470 - no specific mention of it being an adoption blocker but might be implicit
#4961 - no specific mention of it being an adoption blocker but might be implicit. Seems like an amazing productivity improvement.
Bugs:
#7992 - similar to #8503 above but seems to affect a wider range of devices or situations.
#18573 - obvious blocker, Zed doesn't seem to start, related to dual GPU systems
#18422 - no specific mention of it being an adoption blocker but might be implicit
#21146 - no specific mention of it being an adoption blocker but might be implicit
#22426 - no specific mention of it being an adoption blocker but might be implicit
#15925 - no specific mention of it being an adoption blocker but might be implicit
#15231 - no specific mention of it being an adoption blocker but might be implicit
#13190 - no specific mention of it being an adoption blocker but might be implicit. However, #13190 (comment) might be a good idea to implement, if it isn't yet, for debugging memory leaks characteristic to other issues I found.
#6423 ~ 1 comment
The comments represent only comments mentioning that the issue is a blocker. The reactions are only reactions to the mentioned category of comments.
Beta Was this translation helpful? Give feedback.
All reactions