--- title: Neovim to VS Code · DiDoesDigital | daily.dev description: A power user's guide to switching from Neovim to Visual Studio Code. Covers reasons for switching, difficulties with Neovim plugins and language servers, the... canonical: https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Neovim to VS Code · DiDoesDigital | daily.dev og:description: A power user's guide to switching from Neovim to Visual Studio Code. Covers reasons for switching, difficulties with Neovim plugins and language servers, the... og:url: https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp og:image: https://api.daily.dev/og/posts/re11AtNXp.png og:image:alt: Neovim to VS Code · DiDoesDigital og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Neovim to VS Code · DiDoesDigital **[Lobsters](https://daily.dev/sources/lobsters)** · 12 min read · 11 upvotes · 11 comments ## Summary A power user's guide to switching from Neovim to Visual Studio Code. Covers reasons for switching, difficulties with Neovim plugins and language servers, the appeal of VS Code's extension ecosystem, and tips for using both editors in parallel. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@nevenbridge** · 0 upvotes > I used nvim (lazyvim) for 1 month, then i switched back to vscode. Vim is fast, cool (make you feel like a movie hacker) but uncomfortable. --- Tags: [#devtools](https://daily.dev/tags/devtools), [#vim](https://daily.dev/tags/vim), [#vscode](https://daily.dev/tags/vscode), [#webdev](https://daily.dev/tags/webdev) [View this post on daily.dev](https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Neovim to VS Code · DiDoesDigital","url":"https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp"},"datePublished":"2024-05-02T08:08:37.532Z","dateModified":"2026-03-15T06:28:40.561Z","description":"A power user's guide to switching from Neovim to Visual Studio Code. Covers reasons for switching, difficulties with Neovim plugins and language servers, the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a35d580de03c668622afc378c78bbb4a?_a=AQAEuiZ","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a35d580de03c668622afc378c78bbb4a?_a=AQAEuiZ","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":11,"discussionUrl":"https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":11},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":11}],"keywords":"devtools,vim,vscode,webdev","timeRequired":"PT12M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Neovim to VS Code · DiDoesDigital"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/neovim-to-vs-code-didoesdigital-re11atnxp","comment":[{"@type":"Comment","text":"I used nvim (lazyvim) for 1 month, then i switched back to vscode. Vim is fast, cool (make you feel like a movie hacker) but uncomfortable.","datePublished":"2024-05-19T04:06:23.233Z","dateModified":"2024-05-19T10:54:40.946Z","url":"https://daily.dev/posts/re11AtNXp#c-LpwaJ2u9b","author":{"@type":"Person","name":"Antonio Colagreco","url":"https://daily.dev/nevenbridge","image":"https://media.daily.dev/image/upload/s--EvIhErkj--/f_auto/v1789496756/avatars/avatar_ZnsXgbQH5zbzmQV6UA5RA?_a=BAMAMicg0"}}]} ```