From 65556599e8e0e8d4b00f1e43c2b7645db6ee00dc Mon Sep 17 00:00:00 2001 From: Matthew Lemon Date: Mon, 15 May 2023 17:07:07 +0100 Subject: Stream update --- content/stream/2023_05_15.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 content/stream/2023_05_15.md diff --git a/content/stream/2023_05_15.md b/content/stream/2023_05_15.md new file mode 100644 index 0000000..02e58dd --- /dev/null +++ b/content/stream/2023_05_15.md @@ -0,0 +1,14 @@ +--- +title: "2023_05_15" +date: 2023-05-15T16:56:53+01:00 +draft: false +tags: ['vscode', 'linux'] +--- + +After many years of slagging off VSCode and being a total vim snob (and oftentimes an Emacs snob - even worse), today I did a big switch to VSCode. + +Reasons: + +- Neovim - I was pulled in by the most recent hype, mainly on YouTube, and the promise of a Lua-saturated nirvana. Lua does look pretty cool and Neovim is clearly a good editor once you trick it out, but tricking it out was the problem... Too much work. VSCode does most of it anyway. +- The terminal. Managing two main work computers, on two different operating systems (Arch and Debian, having ditched NixOS recently, [as promised](https://yulqen.org/blog/quietly_moving_on_from_nixos/)), I've spent quite a lot of time recently getting my *terminal* in good shape. I've come to realise that life is a little too short to be back-and-forthing it between st, xterm (both of which have esoteric configuration requirements to say the least), gnome and alacritty. I just want to be able to Ctrl+V to paste into a buffer/file/window. +- VSCode is pretty good. I don't like Electron, but I'll live with it. It's just snappy enough. Plus, with some minimal configuration, I can translate most of my primciple vim bindings over. \ No newline at end of file -- cgit v1.2.3