The standardizing on VS code is one of the saddest developments over the last several years IMHO. I think it's great that VS Code exists, but we're headed for a world where you have to use VS Code if you want the best tooling because it won't support other options. The same thing happened with Java dev and IntelliJ, and IMHO it has been extremely unhealthy for the ecosystem. I'm immensely glad that Copilot supports vim, but I'm fearful that it soon won't.
Same could have/could be said about Jetbrains products. People are likely always going to use vim/emacs and create tooling around whatever new hotness exists for them. And honestly? VS Code is just a new iteration on how vim/emacs work in a lot of ways: Providing a place to edit text and then a bunch of plugins that do things with that text.
And if you want vim/emacs to keep living, then you should spend time helping! Create your own extensions, maintain/contribute to existing ones, etc. They will only die out when the last person actively contributing to them stops, so keep the chain of people going :)
> The same thing happened with Java dev and IntelliJ, and IMHO it has been extremely unhealthy for the ecosystem.
While I agree, at the very least IntelliJ stood up on its own as a good IDE. I cut my baby teeth on Eclipse, and as soon as I realised how good IntelliJ is, I jumped ship without looking back. The same can barely be said about VS Code.
If only the depth of our feelings for Emacs counted for more in the market.
There's an argument that music and the arts are dumbed down by the fact that, for instance, making an album worth $10 to millions of people pays way better than making an album worth a million dollars to tens of people, since the album is going to get priced at $10 one way or the other. It only just now occurred to me that the same phenomenon applies to tools.
I've hacked together a basic Emacs ollama api integration that does simplistic code completion against a local LLM from someone else's copilot example. It's slower than I want (about 7 seconds per inference on my M1 mac, typically) and very stupid about what context it sends, but nevertheless: it's just, and only just, enough to be useful. Hadn't considered publishing it because it relies on a python façade to convert copilot-style requests and responses back and forth to ollama, but if there's interest I'll spruce it up and get it out.
I have been a vs code power user and switched to pycharm two years ago and will never go back because of the features for working with multiple environments and projects in pycharm.
Working with phind needs to be available in pycharm for me considering switching from gpt4 to phind.
Chatting with phind on my local files is the feature I am looking for.
