3 ms·
I don't really see why Nova should attempt to be compatible with another editor just because they landed on JS as the integration language. It's doubtful that V
by Skinney 5y ago
I don't really see why Nova should attempt to be compatible with another editor just because they landed on JS as the integration language. It's doubtful that VS Code has the best API, and it's doubtful that VS Code's API is the best fit when the editor isn't primarily rendering HTML.
Because the editor works very differently, it's unlikely they'd ever manage to make the APIs completely compatible, and because of that it'd unlikely that you'd have much porting between the editors anyhow.
There are many editors out there with incompatible plugin APIs (sublime, vim, emacs, vs code, fleet etc.). There is room for Nova to do their own thing, and do their own thing better without catering to the crowd of another editor.
- Klonoar 5y ago>There are many editors out there with incompatible plugin APIs (sublime, vim, emacs, vs code, fleet etc.). There is room for Nova to do their own thing, and do their own thing better without catering to the crowd of another editor. No, there's really not. The marketshare for a native-macOS editor is comparatively small, and they would be better served just making it work and interop well. There is nothing special about their extensions API and there is no glory in re-forging this path.