My argument, based on this thread alone, would be that Codium will always be... held back by its roots in open core project, with some amazing features (like remote editing) or plugins being unavailable. Codium developers do not "own" their core platform (they can't really fork it without breaking plugins), and they don't have much (if any) say in the future direction of it.
Given that it's not unreasonable to think that VS Code is not really that open, and a more desirable outcome would be for developers to support more open alternatives.
CoastalCoder|3 years ago
That said, it sounds like people are maintaining an equivalent store for Codium [0], and are populating it with most of the packages found in Microsoft's repo. I'd think addresses most of the concerns about that particular form of moating.
> with some amazing features (like remote editing) or plugins being unavailable
The remote-editing package is definitely a sticking point for me. Is there some reason to believe that an open-source equivalent is out of reach?
I'm speaking from a place of ignorance on this, but I'd expect someone out there to want to do the work of writing that OSS package. Particularly if they preferred Codium over Vim/Emacs for other reasons.