I will never understand why #vscode defaults to not adding a newline at the end of the file
At least in UNIX-like systems, line feeds are line terminators. Many tools expect there to be a newline after the last line. Most text editors include a newline at the end of the file. VSCode's strange default causes lots of projects to end up with files without a final newline, and causes git churn where people add and remove trailing newlines. #microsoft#programming
Finally I switch to #vscode for developing front end work. It's super useful to see the converted class for #tailwindcss (I'm a beginner). I know there is lsp-tailwind, but I use eglot, and it cannot have multiple lsp server in one major mode yet.
I tuned in to @GurgleApps live stream on YouTube (I saw it was happening via their toot, and I've watched some of their other videos before). I unexpectedly won the "duck race" contest - with an on-brand, digital purple duck! Fun, and they are a nice group who get excited about all kinds of tech, super engaging. Also, I should be getting a #VSCode coaster from them! Check out their shop. https://www.etsy.com/uk/shop/GurgleApps
Join us tonight 7pm UTC for our live stream. Look forward to seeing you. Details in our promo below. Raspberry Pi Pico Pinout Coaster or VSCode Coaster Giveaway included. Link below takes you to the live stream & get notified! @RaspberryPi_org #vscode#electronics#raspberryPiPico
Protip for VS Code users: if VS Code is acting slow, it's probably your extensions' fault. Disable as many as you can. You can also look in the Output tab for "Extension Host" to see what's going on. Can be crazy how many extensions are doing things every time you type a character!
Up until 4 years ago or something #Vim (or #GVim) was my code editor of choice. But when having to work with #PHP#WordPress I preferred #VSCode, which has become my main editor.
With Vim I could never get IntelliSense to work properly so I dropped that.
Currently want to look into working with (Mac)Vim again. But my #vimfiles are sorely outdated (8-12 years or so!). Time for a fresh start. Used to copy plugin's etc. to my vimfiles, but is there a better way these days to also stay up-to-date?
On the left, #VSCode; this app is using ~470 MB of RAM. There's a lot going on in the background here, a web browser engine, a JavaScript engine and server backend. On the right is Visual Basic 6 (#VB6), with a very large project open, taking up 42 MB RAM. Now this isn't even to complain about bloat because VScode performs really well and is very extensible. It's the only editor I've enjoyed using since #TextMate on MacOS;
TIme for the usual end-of-the-week #Linux and #OpenSource News video!
In this one, we have #Microsoft doubling down on errors, with #VSCode dropping #Ubuntu 18.04 without any warning (which is a problem, because auto updates are a very common thing), and #Edge grabbing browsing data from #Chrome without asking for consent.
We also have #Fedora 40 KDE going back a bit on their removal of X11, and some unintended consequences of #RedHat licensing changes:
About 3 months ago, there was an updated issue which needed community feedback, but (I guess) no-one knew about it, so it got closed.
It got re-opened (don’t know why) but unless Django folks actually say, “Yes we use VS Code, and that it doesn’t support the Django test runner is a PITA”, that the same will happen.
#VisualStudioCode now has a multi-file diff view. Just click the "View Changes" button in the Source Control pane instead of clicking on each individual file 😎 An experience more like viewing a PR on GitHub. #VSCode#code