Some thoughts on what I'd think would be requirements for a step function improvement in code editors for the new age: - Human collaboration is a first class c

Some thoughts on what I'd think would be requirements for a step function improvement in code editors for the new age: - Human collaboration is a first class citizen if not the main design pillar. Instead of having add extensions for git, github etc. these need to be baked into the IDE. In-line blame, graph/UI for git history, diffs, team code editing etc. - Basic code assistance utilities: Intellisense, Linting, Static Analysis, Formatting, Docstring Preview, Type Hinting, Dependency graphs, Code Metadata should again be key features that ships with the IDE as opposed to being enabled through extensions. - Modern AI based code assistance: in-line code assistive comments based on review of what you wrote, tab autocomplete (this is covered well by the AI code editors/extensions), automatic documentation - Implementation in C/Rust with effective/efficient usage of compute resources. Zed does do this - Baking in project management/collab from JIRA/Linear: This would be the only way to keep human engineers collaboration not woefully slower than AI 'engineers' who would automatically bug fix, push, do PRs, review PRs etc.