From e3dce7e0e51d0a8829469d189d6a4da375f432fa Mon Sep 17 00:00:00 2001 From: Philipp Hansch Date: Mon, 19 Aug 2024 17:06:00 +0200 Subject: [PATCH] Add new note --- content/notes/2024-08-19-vscode.md | 31 ++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 content/notes/2024-08-19-vscode.md diff --git a/content/notes/2024-08-19-vscode.md b/content/notes/2024-08-19-vscode.md new file mode 100644 index 00000000..5f6f88f7 --- /dev/null +++ b/content/notes/2024-08-19-vscode.md @@ -0,0 +1,31 @@ ++++ +title = "I gave VSCode a try for 9 months" ++++ + +There's probably a full blog post in here somewhere. For the past few months +I've been using VSCode for work and private projects. I grew tired of +breaking plugins and changing configs all the time. I'm a big fan of robust +tech and my neovim experience has been very far from that. I want to spend as +little time as possible thinking about configs. The majority of my computer +time should not be spent working on my [dotfiles]. + +VSCode solves this problem by having plugins that almost always just work. +Especially when it comes to Language Server plugins, there's a world of +difference. So around 9 months ago I started using VSCode as my main editor. + +Fast-forward to today, there are two main reasons I'm now switching back to +neovim: + +* VSCode ended up being a memory hog on my Dell XPS 13 from 2018. I ran out of +memory multiple times. +* The UI of VSCode is distracting and annoying to use. + +Now I'm using [LazyVim] to take care of my LSP setup and hope that it doesn't +break as often. I essentially outsourced most of my neovim configuration. I can still +configure neovim to have a distraction-free UI, be resource-friendly and most +important, not break on every plugin update. + +Let's see what it looks like after another 9 months. + +[LazyVim]: http://www.lazyvim.org/ +[dotfiles]: https://github.com/phansch/dotfiles