<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Visual Studio Code on Alemasone</title><link>https://www.alemasone.com/en/tags/visual-studio-code/</link><description>Recent content in Visual Studio Code on Alemasone</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 19 Sep 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://www.alemasone.com/en/tags/visual-studio-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Must-Have VS Code Extensions You Should Install Now</title><link>https://www.alemasone.com/en/best-vs-code-extensions-to-install/</link><pubDate>Thu, 17 Oct 2024 21:57:04 +0000</pubDate><guid>https://www.alemasone.com/en/best-vs-code-extensions-to-install/</guid><description>&lt;div class="lead !mb-9 text-xl"&gt;&#10; Having thirty extensions installed is a problem, not a configuration. Each one slows down startup, consumes memory, and can conflict with others. The ones you actually need can be counted on the fingers of two hands, and many things that required an extension years ago are now built directly into Visual Studio Code.&#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;Before adding anything, look at what the editor already does: format on save, renaming symbols across the entire project, Git, terminal, find and replace with regular expressions, multiple cursors, Markdown preview, settings sync, JavaScript debugging in the browser, and bracket pair colorization. For those last three, until a few years ago, you needed Settings Sync, Debugger for Chrome, and Bracket Pair Colorizer: if you still have them, you can remove them.&lt;/p&gt;</description></item><item><title>How to Install C and C++ Compilers on Windows, Linux &amp; macOS</title><link>https://www.alemasone.com/en/install-c-cpp-compilers-windows-linux-macos/</link><pubDate>Sat, 20 Jul 2024 11:22:37 +0000</pubDate><guid>https://www.alemasone.com/en/install-c-cpp-compilers-windows-linux-macos/</guid><description>&lt;div class="lead !mb-9 text-xl"&gt;&#10; On Linux and macOS, the compiler is installed with a single command. On Windows, the right way to do it today is &lt;strong&gt;MSYS2&lt;/strong&gt;, which provides GCC via MinGW-w64 and handles updates automatically. The old SourceForge MinGW—the one with the Installation Manager you’ll see in many guides (including the first version of this one)—has been stagnant for years, only produces 32-bit programs, and should no longer be used.&#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;A compiler transforms source code into an executable program. For C and C++, there are two main ones: &lt;strong&gt;GCC&lt;/strong&gt;, around since 1987 and available everywhere, and &lt;strong&gt;&lt;a href="https://clang.llvm.org/" target="_blank" rel="noreferrer"&gt;Clang&lt;/a&gt;&lt;/strong&gt;, which is younger, provides clearer error messages, and is the default on macOS. The latest version of GCC is 16, released in April 2026, which uses the C++20 standard by default for C++.&lt;/p&gt;</description></item></channel></rss>