5 ms·

> the big exception being VSCode for Typescript/JS Why? As a neovim user with a lot of ts/js at $job, curious what if I'm missing especially useful (outside of

• dmix 4y ago
  Almost entirely because I develop Vue 3 w/ Vite on top of Rails 7 (plus a very opinionated Eslint + Prettier set up) so cutting edge plugin support = key, combined with a team that uses a mix of Vim and other stuff. VSCode's community will always completely dominate Vim for Typescript support and it's far easier to establish VSCode as the standard editor than a mix of custom Vim configs. Even the base Vue VSCode plugin + native TS engine doesn't support my needs for modern Vue 3 <script setup /> syntax without a ton of false positive redline errors. When I switched to using Volar my life became way easier (Neovims LSP plugins are usually a year behind the VSCode native ones let alone plugins): https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin https://marketplace.visualstudio.com/items?itemName=Vue.vsco... Otherwise our Ruby backend devs can use what they want. So can frontend but they'll be constantly fighting the current.