Replies: 1 comment 2 replies
-
We are currently building our Extensions API. Our thought was because the two editors have completely different architectures, running VS Code extensions in CodeEdit would be next to impossible to do. If you want to help us shape our Extensions API and try to get this runtime working, I wouldn't be opposed to it. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am working on VSCode Extension Runtime, a language-agnostic way of running VSCode extensions on other code-editors/IDEs.
Was browsing through GitHub and this project looked like a good candidate for implementing this, since Mac users generally prefer native UIs, but still need something like VSCode for many programming languages. XCode is full of shit, it's a good IDE for certain things but it's heavy.
What do you think? Does this look like a good idea to you?
Of course, this runtime would be entirely optional, maybe opt-in. But it would be a good way of extending Code Edit in a lightweight way, with the native UI, and the ecosystem of VSCode extensions.
Implementing this is not easy to do/maintain.
Does CodeEdit already have some extension system? This would make the task much easier for you to maintain the core of CodeEdit and for me to work separately.
Beta Was this translation helpful? Give feedback.
All reactions