3 ms·
This is probably the main reason why I won’t use it anymore: Microsoft is repeating in VSCode all the things it did in the Windows/IE era.
by fiddlerwoaroof 3y ago
This is probably the main reason why I won’t use it anymore: Microsoft is repeating in VSCode all the things it did in the Windows/IE era.
- xarope 3y agoFirst thing I did in VScode was install/activate Vim mode. So if VScode does go the way of Windows, then I'll "just" go back to another editor with vi bindings. (yes yes, I remember some of my emacs bindings, wrote a thesis in latex on emacs, and learnt lisp as a result, but I realised that vi was more "portable")
- kapitanluffy 3y agobtw, Sublime Text has a built in vim bindings albeit disabled by default. I suggest you give it a try.
- demondemidi 3y ago> Microsoft is repeating in VSCode all the things it did in the Windows/IE era. Example?
- fiddlerwoaroof 3y agoThey embraced open source software and open protocols like LSP to get as many programming languages working with VSCode as possible and then they licensed their own pylance language server so that you can’t use it outside of VSCode.