# wsl Published articles for wsl. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Evolution of WSL Support in JetBrains IDEs DevFeed: [The Evolution of WSL Support in JetBrains IDEs]() Original publisher: [Read original article]() Author: Kristina Pchelintseva Published: 2026-09-09T10:39:49Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [Processes]() Tags: [2026-2](), [architecture](), [debug](), [ecosystem](), [engineering](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [linux](), [phpstorm](), [remote-development](), [support](), [webstorm](), [windows](), [wsl]() ### AI overview JetBrains describes its evolution of WSL integration and recommends Native mode from version 2026.2. In this mode, supported IDEs remain Windows applications while an agent in WSL handles project files and processes. ### Source excerpt JetBrains IDEs have worked with WSL for many years, and over time, several ways of using it have emerged across our products. Depending on the entry point, the IDE could rely on a different underlying architecture, leading to a different experience. Starting with the 2026.2 release, there is one recommended entry point. In IntelliJ IDEA, [...] ## Podman 6.1.0: Volume Renaming, Machine Restarts, and a Long List of Bug Fixes DevFeed: [Podman 6.1.0: Volume Renaming, Machine Restarts, and a Long List of Bug Fixes]() Original publisher: [Read original article]() Author: Mohan Boddu Published: 2026-08-17T19:51:34Z Content type: release Language: en Sources: [blog.podman.io]() Topics: [podman](), [podman machine](), [API](), [Containers](), [macOS](), [Windows](), [Windows Subsystem for Linux](), [Docker]() Tags: [announcement](), [api](), [articles](), [blog](), [bug-fixes](), [buildah](), [containers](), [docker](), [macos](), [new-feature](), [podman](), [podman-desktop](), [podman-machine](), [release](), [releases](), [update](), [volume](), [windows](), [wsl]() ### AI overview Podman 6.1.0 adds volume renaming, a dedicated podman machine restart command, idempotent network removal, retry options for manifest pushes, improved Kubernetes healthcheck mapping, WSL port-forwarding support, IPv6 forwarding fixes, and free-memory reporting. It also improves Docker-compatible API behavior and includes numerous bug fixes and dependency updates. ### Source excerpt Podman 6.1.0 is here, and while it's not a flashy release, it's the kind of update that quietly makes day-to-day container work smoother. This release focuses on rounding out long-requested quality-of-life commands, tightening up podman machine reliability across Windows, macOS, and WSL, and squashing a healthy batch of bugs in Quadlet, healthchecks, and the API [...] ## \[May-Jun 2026\] AI Community -- Activity Highlights and Achievements DevFeed: [\[May-Jun 2026\] AI Community -- Activity Highlights and Achievements]() Original publisher: [Read original article]() Author: Nari Yoon Published: 2026-07-22T01:22:04Z Content type: article Language: en Sources: [Google Developer Experts - Medium]() Topics: [google-antigravity](), [Google](), [Google AI](), [AI Agent](), [Agent Skills](), [Model Context Protocol (MCP)](), [Windows Subsystem for Linux](), [Python](), [HTML](), [Command-line interface](), [CSV](), [SDKs]() Tags: [2026](), [ai](), [ai-agent](), [ai-agents](), [antigravity](), [cli](), [community](), [google](), [google-ai](), [here](), [html](), [mcp](), [python](), [sdk](), [skills](), [wsl]() ### AI overview This article highlights May-June 2026 activities and achievements from Google AI communities. It summarizes community projects, codelabs, experiments, and guides involving Google Antigravity, Gemini, the Antigravity SDK, AI agents, MCP servers, agent skills, CLI and IDE workflows, HTML dashboards, CSV data, and Windows Subsystem for Linux. ### Source excerpt We love sharing the accomplishments of the Google AI communities over the month. We appreciate all the hard work and dedication of our community members. Without further ado, here are the key highlights by products! Agentic DevelopmentAntigravity [Codelab] Building Trustable AI at 100 MPH by GDEs in the US: Hemanth HM, Vikram Tiwari, Lynn Langit, Sebastian Gomez, Rabimba Karanjai; Googler: Ajeet Mirwani; and the partner: Ocupop guides you in building a trustable AI prototype inspired by the field test from the Unstoppable GDE Cohort. The project summary, Bridging the Domain Gap: AI Race Coach built with Antigravity and Gemini and the members of the July cohort were featured on Google for Developers Blog✨. Skills over System Prompts: Building an Anki Tutor with the Antigravity SDK by AI GDE Ertuğrul Demir (Türkiye) demonstrates the value of a modular approach to AI agent design by creating custom Python tools and reusable skill packages for an Anki flashcard tutor using Antigravity SDK. (Image source) Startup on a Shoestring -- Building with a 50c Budget using Google Antigravity Cost & Token Monitors💸 by AI GDE Jigyasa Grover (US) conducted an SDK-powered cost engineering experiment to observe an AI agent prioritize, panic, and ship an MVP landing page under intense budget pressure. Google Antigravity CLI: Orchestrating Parallel AI Agents by AI GDE Aashi Dutt (India) explores how to create an interactive HTML dashboard from a raw CSV file with a single command and explains the benefits of the subagent architecture. (Image source) Configuring MCP Servers and Skills for Antigravity CLI and IDE by Cloud GDE Darren Lester (UK) provides a deep-dive guide on configuring MCP servers and agent skills for the new Antigravity CLI and IDE. He also shared Resolving WSL Friction with Google Antigravity: the Agy 2.0 and Agy IDE Edition discussing how to resolve friction between the Antigravity suite and the Windows Subsystem for Linux environment. Google Antigravity 2 & Gemini 3.5 ## Automatic CA Certificate Import in Podman 6 DevFeed: [Automatic CA Certificate Import in Podman 6]() Original publisher: [Read original article]() Author: Mario Loriedo Published: 2026-07-08T09:26:23Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [Containers](), [cross-platform](), [configuration](), [Go](), [Linux](), [macOS](), [Windows](), [Windows Subsystem for Linux]() Tags: [announcement](), [articles](), [certificates](), [community](), [configuration](), [containers](), [cross-platform](), [developers](), [enterprise](), [go](), [linux](), [macos](), [new-feature](), [podman](), [podman-machine](), [providers](), [qemu](), [security](), [windows](), [wsl]() ### AI overview Podman 6 introduces optional automatic import of trusted host CA certificates into Podman Machine guests. The feature synchronizes certificates on machine boot, helping containers access internal registries and web services without manual certificate export and injection. ### Source excerpt With the release of Podman 6.0, an improvement for enterprise users and developers behind corporate proxies is the new automatic import of host certificates for the Podman machine. ## How Our Community Shipped 66 Git Improvements In Under 2 Months DevFeed: [How Our Community Shipped 66 Git Improvements In Under 2 Months]() Original publisher: [Read original article]() Author: Katie Geer, Esther Trapadoux, Cole Miller Published: 2026-02-05T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Git](), [Pull Request](), [ssh](), [Windows Subsystem for Linux]() Tags: [bug-fixes](), [community](), [contributions](), [contributors](), [git](), [improvements](), [ssh](), [wsl]() ### AI overview Zed describes an eight-week community challenge that improved its Git experience through contributor pairing, project planning, and demos. The program shipped 66 contributions, including five major features, 28 bug fixes, and 33 other improvements. The article highlights file Git history and a directory-based tree view as examples. ### Source excerpt A celebration of the Zed community's eight-week sprint to make Git in Zed better than ever. ## Zed Is Now Available on Windows DevFeed: [Zed Is Now Available on Windows]() Original publisher: [Read original article]() Author: Max Brunsfeld Published: 2025-10-15T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Windows](), [Windows Subsystem for Linux](), [Claude Code]() Tags: [directx](), [github](), [testing](), [webassembly](), [windows](), [wsl]() ### AI overview Zed has released a stable Windows version with weekly updates and a preview channel. The Windows build uses DirectX 11 and DirectWrite, integrates with WSL and SSH remoting, supports extensions, and includes Zed's AI features. ### Source excerpt Zed for Windows is finally here. Download it today. ## Python in Visual Studio Code - October 2025 Release DevFeed: [Python in Visual Studio Code - October 2025 Release]() Original publisher: [Read original article]() Author: Luciana Abud Published: 2025-10-10T17:55:26Z Content type: release Language: en Sources: [Microsoft Python Engineering]() Topics: [Python](), [Visual Studio Code](), [releases](), [Testing](), [Pytest](), [.NET 11](), [Windows Subsystem for Linux](), [GitHub Copilot](), [jupyter]() Tags: [2025](), [github-copilot](), [powershell](), [pytest](), [python](), [release](), [releases](), [testing](), [visual-studio-code](), [wsl]() ### AI overview Microsoft announces the October 2025 release of the Python extensions for Visual Studio Code. The update improves Python environment handling, adds a Copy Test ID option for pytest functions, and makes Python virtual-environment activation more reliable across shell creation methods, PowerShell, and WSL. ### Source excerpt The October 2025 release of the Python and Jupyter extensions for Visual Studio Code are now available. This release includes improvements to the Python Environments extension, Copy Test ID functionality, and enhanced environment activation when using Copilot Chat. Keep on reading to learn more! The post Python in Visual Studio Code - October 2025 Release appeared first on Microsoft for Python Developers Blog. ## Troubleshooting 'An Unexpected Error While Executing WSL Command' in Docker Desktop DevFeed: [Troubleshooting 'An Unexpected Error While Executing WSL Command' in Docker Desktop]() Original publisher: [Read original article]() Author: Youssef Salem Published: 2025-08-27T21:53:50Z Content type: tutorial Language: en Sources: [Baeldung - Ops]() Topics: [Windows Subsystem for Linux](), [Docker](), [PowerShell](), [Windows]() Tags: [docker](), [docker-docker-image](), [docker-image](), [powershell](), [troubleshooting](), [tutorial](), [wsl](), [wsl2]() ### AI overview A tutorial explains how to troubleshoot the "An Unexpected Error Was Encountered While Executing a WSL Command" message in Docker Desktop on Windows with the WSL2 backend. It describes how Docker and WSL interact, outlines causes such as stopped services, outdated versions, corrupted distributions, permissions, and resource limits, and begins a step-by-step process using WSL checks and PowerShell commands. ### Source excerpt Discover how Docker and WSL interact in order to troubleshoort this error: "An Unexpected Error While Executing WSL Command" Related Stories What Is the Runtime Performance Cost of a Docker Container? Docker Build and Run Platforms and Resolving exec /usr/bin/sh: exec format error Using a Package Manager in GitHub Actions ## Enhance productivity with AI + Remote Dev DevFeed: [Enhance productivity with AI + Remote Dev]() Original publisher: [Read original article]() Author: Brigit Murtaugh, Christof Marti, Josh Spicer, Olivia Guzzardo McVicker Published: 2025-05-27T00:00:00Z Content type: article Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [remote-development](), [Visual Studio Code](), [Artificial Intelligence](), [GitHub Copilot](), [Containers](), [Large Language Model](), [ssh](), [Windows Subsystem for Linux]() Tags: [ai](), [ai-coding](), [article](), [blog](), [container-based-application](), [containers](), [copilot](), [dev](), [developer](), [developer-productivity](), [development](), [github](), [github-copilot](), [linux](), [llm](), [productivity](), [remote](), [ssh](), [vs-code](), [windows](), [wsl]() ### AI overview This VS Code article explains how AI, including GitHub Copilot, can enhance Remote Development workflows. It covers contextual chat, remote installation, assistance with setup and debugging, custom instructions, chat participants, tool approvals, and isolated autonomous coding sessions across SSH, Dev Containers, WSL, tunnels, and GitHub Codespaces. ### Source excerpt Enhance your developer productivity with AI and Remote Development. Read the full article ## Bringing DHH's Omakub to WSL2? DevFeed: [Bringing DHH's Omakub to WSL2?]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2024-11-05T18:15:59Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Windows Subsystem for Linux](), [WSL2](), [Ubuntu](), [Windows](), [PowerShell](), [Rust]() Tags: [alacritty](), [developer-setup](), [linux](), [omakub](), [powershell](), [rust](), [ubuntu](), [windows](), [wsl](), [wsl2](), [zellij]() ### AI overview A tutorial on setting up a WSL2 developer environment inspired by DHH's Omakub, including Alacritty, Zellij, Cargo, Ubuntu, and the Tokyo Night theme. ### Source excerpt Setting up a developer environment on WSL2 with Alacritty, Zellij, Cargo and the Tokyo Night theme inspired by DHH's Omakub. ## Working with Espressif's SoCs using WSL2 DevFeed: [Working with Espressif's SoCs using WSL2]() Original publisher: [Read original article]() Author: John Lee Published: 2024-11-04T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Windows Subsystem for Linux](), [ESP-IDF](), [Espressif](), [USB](), [Windows](), [ESP32-C6]() Tags: [blog](), [devkit](), [esp-idf](), [espressif](), [flashing](), [guide](), [installation](), [monitoring](), [troubleshooting](), [usb](), [windows](), [wsl](), [wsl2]() ### AI overview A step-by-step guide to developing with Espressif SoCs from WSL2. It explains USB serial-port forwarding with USBIPD-WIN, including installation, attaching and detaching a devkit, and troubleshooting kernel-module support. ### Source excerpt Released in 2016 by Microsoft, the Windows Subsystem for Linux (WSL) is a feature that allows the use of a Linux environment with no need of a virtual machine, container or dual boot. The WSL is a great way to run Linux alongside Windows. Introduction# In some cases, users can't use Windows PowerShell for developing ESP-IDF applications for ESP SoCs, or when WSL is already in use, the flashing and monitoring steps can be tricky. ## Using WSL and Let's Encrypt to create Azure App Service SSL Wildcard Certificates DevFeed: [Using WSL and Let's Encrypt to create Azure App Service SSL Wildcard Certificates]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2023-06-27T17:17:25Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [Azure](), [Windows Subsystem for Linux](), [SSL](), [openssl](), [apt](), [pip]() Tags: [apt](), [azure](), [certificates](), [dns](), [install](), [openssl](), [password](), [private-key](), [ssl](), [windows](), [wsl]() ### AI overview This tutorial explains how to use Certbot in Windows Subsystem for Linux with Let's Encrypt to create a wildcard certificate, convert it to a password-protected PFX containing the certificate chain, and upload it to Azure App Service. It also describes importing and exporting the certificate in Windows before updating the App Service binding. ### Source excerpt There are many let's encrypt automatic tools for azure but I also wanted to see if I could use certbot in wsl to generate a wildcard certificate for the azure Friday website and then upload the resulting certificates to azure app service. Azure app service ultimately needs a specific format called dot PFX that includes the full certificate path and all intermediates. Per the docs, App Service private certificates must meet the following requirements: Exported as a password-protected PFX file, encrypted using triple DES. Contains private key at least 2048 bits long Contains all intermediate certificates and the root certificate in the certificate chain. If you have a PFX that doesn't meet all these requirements you can have Windows reencrypt the file. I use WSL and certbot to create the cert, then I import/export in Windows and upload the resulting PFX. Within WSL, install certbot: sudo apt update sudo apt install python3 python3-venv libaugeas0 sudo python3 -m venv /opt/certbot/ sudo /opt/certbot/bin/pip install --upgrade pip sudo /opt/certbot/bin/pip install certbot Then I generate the cert. You'll get a nice text UI from certbot and update your DNS as a verification challenge. Change this to make sure it's two lines, and your domains and subdomains are correct and your paths are correct. sudo certbot certonly --manual --preferred-challenges=dns --email YOUR@EMAIL.COM --server https://acme-v02.api.letsencrypt.org/directory --agree-tos --manual-public-ip-logging-ok -d "azurefriday.com" -d "*.azurefriday.com" sudo openssl pkcs12 -export -out AzureFriday2023.pfx -inkey /etc/letsencrypt/live/azurefriday.com/privkey.pem -in /etc/letsencrypt/live/azurefriday.com/fullchain.pem I then copy the resulting file to my desktop (check your desktop path) so it's now in the Windows world. sudo cp AzureFriday2023.pfx /mnt/c/Users/Scott/OneDrive/Desktop Now from Windows, import the PFX, note the thumbprint and export that cert. Import-PfxCertificate -FilePath "AzureFriday2023.pfx" - ## Node.js 17.4.0 (Current) DevFeed: [Node.js 17.4.0 (Current)]() Original publisher: [Read original article]() Published: 2022-01-18T15:07:53Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [cross-platform](), [Open Source](), [servers](), [Command-line interface](), [V8](), [Git]() Tags: [benchmark](), [command-line](), [cross-platform](), [git](), [javascript](), [libuv](), [node-js](), [npm](), [open-source](), [python](), [servers](), [ubuntu](), [workflow](), [wsl]() ### AI overview Node.js 17.4.0 is a current release with semver-minor additions and fixes across child_process, crypto, events, loaders, streams, async_hooks, build tooling, and dependencies. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## GoLand 2021.3: полная поддержка WSL, запуск gofmt при сохранении файла, Inline Function, удаленная разработка DevFeed: [GoLand 2021.3: полная поддержка WSL, запуск gofmt при сохранении файла, Inline Function, удаленная разработка]() Original publisher: [Read original article]() Author: asspirin12 (JetBrains) Published: 2021-12-15T12:53:19Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [Windows Subsystem for Linux](), [ide](), [gRPC](), [HTTP](), [SDK](), [App]() Tags: [code](), [go](), [http](), [ide](), [jetbrains](), [sdk](), [tag-2c039dce53be](), [toolbox](), [toolbox-app](), [wsl]() ### AI overview JetBrains describes the GoLand 2021.3 release, including full WSL support, gofmt on save by default, an Inline Function refactoring, beta remote development, gRPC support in the HTTP client, and debugger improvements. ### Source excerpt Привет, Хабр! Сегодня расскажем о свежем релизе GoLand. Что нового: полная поддержка WSL, запуск gofmt при сохранении по умолчанию, рефакторинг Inline Function, удаленная разработка (Beta), поддержка gRPC в HTTP-клиенте, улучшения отладчика и многое другое! Под катом подробный разбор новых возможностей с гифками. Скачать GoLand 2021.3 можно на сайте JetBrains или через приложение Toolbox App. Читать далее ## Релиз CLion 2021.2: улучшения в отладчике, проверка времени жизни объектов, поддержка CMake Presets DevFeed: [Релиз CLion 2021.2: улучшения в отладчике, проверка времени жизни объектов, поддержка CMake Presets]() Original publisher: [Read original article]() Author: anastasiak2512 (JetBrains) Published: 2021-07-29T13:29:29Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [CLion](), [C++](), [CMake](), [ide](), [Windows Subsystem for Linux](), [MSVC]() Tags: [autotools](), [c-plus-plus](), [cling](), [clion](), [cmake](), [debugger](), [freertos](), [ide](), [lifetimes](), [make](), [msvc](), [windows](), [wsl]() ### AI overview JetBrains presents CLion 2021.2, a cross-platform IDE for C and C++. The release adds protection against common C++ memory-access problems, CMake Build Presets support, GNU Autotools project support, remote-host and WSL profiling, debugger improvements, and Cling integration. ### Source excerpt Привет, Хабр! В конце июля в JetBrains стартует очередной релизный "паровоз". На этой неделе обновились многие IDE на платформе IntelliJ, на следующей запланированы обновления наших продуктов для .NET. И сегодня мы хотим поговорить о CLion 2021.2 -- новейшей версии нашей кроссплатформенной IDE для разработки на C и C++. Коротко о главном. CLion 2021.2 защитит ваш код от типичных проблем доступа к памяти в C++, автоматически загрузит настройки сборки приложения из CMake Build Presets, откроет проект с использованием GNU Autotools, поможет с профилированием на удаленном хосте и на WSL. Кроме того, значительно улучшен отладчик (самые крупные обновления ждут наших пользователей на Windows). А для тех, кто пока только изучает C++ или прототипирует новое приложение или библиотеку, мы добавили интеграцию с Cling -- интерпретатором С++. Дьявол в деталях ## Configure Windows Terminal with WSL, Ubuntu, Zsh, and oh-my-zsh DevFeed: [Configure Windows Terminal with WSL, Ubuntu, Zsh, and oh-my-zsh]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-02-23T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Terminal](), [Windows Subsystem for Linux](), [Windows](), [Ubuntu](), [Zsh](), [PowerShell](), [Open Source]() Tags: [guide](), [homelab](), [linux](), [open-source](), [powershell](), [terminal](), [tutorial](), [ubuntu](), [windows](), [wsl]() ### AI overview A tutorial showing how to configure Microsoft Windows Terminal with WSL, install Ubuntu, and set up Zsh and oh-my-zsh. It also describes using Windows and Linux environments alongside PowerShell and cmd. ### Source excerpt Lots of people ask which terminal I use on Windows and how I configure it.It's pretty simple, I use the Microsoft Windows Terminal and it's a fantastic terminal on Windows.It is free and open source.With Windows Terminal, you can install and configure different environments for Windows and Linux.You can choose between Ubuntu or any other WSL 1 or WSL 2 (Windows Subsystem for Linux) environment... ## Tutorial: Self-hosted CI/CD deployment in a homelab with GitLab CI, Docker, and Kubernetes DevFeed: [Tutorial: Self-hosted CI/CD deployment in a homelab with GitLab CI, Docker, and Kubernetes]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-09-12T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [CI/CD](), [GitLab](), [Homelab](), [Docker](), [Kubernetes](), [Docker Image](), [kubectl](), [rancher](), [Dockerfile](), [nginx](), [React](), [Windows]() Tags: [continuous-delivery](), [continuous-integration](), [developer](), [docker](), [docker-container](), [docker-image](), [gitlab-ci](), [guide](), [homelab](), [kubectl](), [kubernetes](), [nginx](), [rancher](), [react](), [registry](), [self-hosted](), [testing](), [unit-tests](), [windows](), [wsl]() ### AI overview This tutorial explains how to set up a self-hosted development pipeline in a homelab. It covers repository setup, unit testing with a GitLab CI runner, building and publishing a Docker image to a container registry, and deploying the container to a self-hosted Kubernetes cluster with kubectl. ### Source excerpt So you're a software engineer or a developer who wants to self-host your own code in your own homelab? Well this is the tutorial for you! In this step-by-step guide we'll walk through setting up a repo, building and testing our own code (with unit tests) in a self-hosted Gitlab CI runner in our CI pipeline, then we'll build a Docker image and push it up to a container registry, then we'll use... ## Nix Package Manager on Ubuntu or Debian DevFeed: [Nix Package Manager on Ubuntu or Debian]() Original publisher: [Read original article]() Published: 2020-05-31T03:11:45Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Nix](), [Package manager](), [Debian](), [Ubuntu](), [Linux](), [Windows Subsystem for Linux]() Tags: [debian](), [install](), [installation](), [linux](), [node-js](), [python](), [ubuntu](), [wsl]() ### AI overview A practical guide to installing and using the Nix package manager on Ubuntu or Debian, including systems running under WSL. It covers single-user installation, a workaround for a WSL 1 issue, verification, package discovery, and using Nix to access newer software and switch between development environments. ### Source excerpt Even though Ubuntu/Debian is equipped with its legendary powerful package manager, dpkg, in some cases, it is still beneficial to take advantage of Nix, a purely functional package manager. ## Setting Up Windows for JavaScript Development with WSL, Node.js, Yarn, VS Code, and Zsh DevFeed: [Setting Up Windows for JavaScript Development with WSL, Node.js, Yarn, VS Code, and Zsh]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-03-12T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Development](), [JavaScript](), [Windows](), [Windows Subsystem for Linux](), [Ubuntu](), [Zsh](), [npm](), [Yarn](), [Command-line interface](), [vs-code]() Tags: [coding](), [install](), [javascript](), [npm](), [tutorial](), [ubuntu](), [vs-code](), [windows](), [wsl]() ### AI overview A beginner tutorial for configuring a Windows machine for JavaScript development. It covers Windows Terminal, WSL, Ubuntu, Zsh with Oh My Zsh, Yarn, npm, NVM, Node.js, VS Code, and Git SSH access to GitHub. ### Source excerpt You want to get started developing JavaScript with NodeJS, ReactJS, or AngularJS but you're not sure how to get started? This is a complete, step by step guide on how to configure your Windows machines for JavaScript development the right way.You'll learn how to install and configure Windows, the new Windows Terminal, WSL, Ubuntu, ZSH with Oh My ZSH, yarn, NPM, NVM, NodeJS, and VS Code.We'll ... ## Node.js 13.1.0 (Current) DevFeed: [Node.js 13.1.0 (Current)]() Original publisher: [Read original article]() Published: 2019-11-06T07:52:53Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [npm](), [Python 3.8](), [Visual Studio](), [Windows Subsystem for Linux]() Tags: [cli](), [cross-platform](), [javascript](), [js](), [node](), [node-js](), [npm](), [open-source](), [python-3-8](), [visual-studio](), [wsl]() ### AI overview Node.js 13.1.0 is a Current release that adds new command-line, crypto, filesystem, and datagram capabilities, updates npm and V8, and includes build, documentation, and performance improvements. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Cross Compiling with Docker on WSL 2 DevFeed: [Cross Compiling with Docker on WSL 2]() Original publisher: [Read original article]() Published: 2019-06-30T21:24:51Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Windows Subsystem for Linux](), [Cross-Compilation](), [Docker](), [qemu](), [C](), [Ubuntu](), [Windows](), [WebAssembly]() Tags: [arm](), [c](), [containers](), [cross-compilation](), [docker](), [qemu](), [ubuntu](), [webassembly](), [windows](), [wsl]() ### AI overview This tutorial explains how to use Docker on WSL 2 to cross-compile a simple C program for ARMv7. It uses Dockcross for Docker-based cross-compilation, QEMU to run the resulting ARM binary, and briefly describes targets including MIPS, PowerPC, Windows, and WebAssembly. ### Source excerpt Now that WSL 2 packs a true Linux kernel and supports Linux containers (via Docker), it can be a perfect setup to perform application cross compilations. ## Why I stuck with Windows for 6 years while developing Discourse DevFeed: [Why I stuck with Windows for 6 years while developing Discourse]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2019-03-31T23:44:35Z Content type: article Language: en Sources: [Sam Saffron]() Topics: [Windows](), [Development](), [Ruby](), [Windows Subsystem for Linux](), [virtualization](), [Benchmark](), [Docker]() Tags: [benchmark](), [blog](), [c-sharp](), [development](), [docker](), [go](), [linux](), [net](), [performance](), [rails](), [ruby](), [rust](), [saffron](), [sam](), [sql](), [virtualization](), [weblog](), [windows](), [wsl]() ### AI overview The author examines the performance cost of developing Discourse on Windows while using WSL or a VMware-based Linux virtual machine. On the author's machine, running specs was 25% slower with WSL and 38% slower with VMware, while WSL also performed poorly with many small files. ### Source excerpt I made this tweet that got reasonably popular: We benchmarked how long it takes to run the Ruby test suite for Discourse across our various dev machines. I can not believe what a crazy tax I have paid over the years insisting on sticking with Windows, highlighted results mine. image824x706 73.7 KB https://twitter.com/samsaffron/status/1111511735851081728 This evoked a lot of extremely strong emotions from various people out there. Ranging from "Sam is a fool what kind of insane benchmark is this", "the real story is MacOS has bad Ruby perf" to a general "Oh no". The core point I was trying to make was that I was paying a pretty high tax for deciding to "stick with with Windows". There are a bunch of other points hiding here that are also worth discussing. Why are you sticking with Windows to run Linux in a VM? https://twitter.com/shanselman/status/1111538525017530371 What I did not know is the extent of the VM tax I was paying regularly. I never dual booted my computer so I had no proper anchoring point of reference. I very strongly believe that many Ruby/Rust/Go/Elixir/Scala and even some Node developers who end up doing the WSL dance or run Linux in a VM for development, or use Linux Docker for dev on Windows are not aware of the full extent of the tax. On my machine the price of admission for using WSL was 25% slowdown in my day to day running of specs. And a 38% slowdown for using a VMware based VM. I am not alone here... other team members have experienced similar slowdowns. Other people out there also experience similar slowdowns. https://twitter.com/stevedesmond_ca/status/1111585969650712578 What I thought was inside my wonderful wish hat was that the performance hit was minor: serverfault.com Is virtual machine slower than the underlying physical machine? virtualization, performance, cloud-computing, benchmark answered by TomTom on 07:25AM - 24 Apr 10 UTC Yes. But that is not the question. The difference is normally negligible (1% to 5%). If you Google, well t ## Windows for Linux Nerds DevFeed: [Windows for Linux Nerds]() Original publisher: [Read original article]() Published: 2017-09-09T15:25:24Z Content type: article Language: en Sources: [Jessie Frazelle]() Topics: [Windows Subsystem for Linux](), [Windows](), [Kernel](), [POSIX]() Tags: [kernel](), [posix](), [windows](), [wsl]() ### AI overview A developer describes learning Windows after joining Microsoft, with a focus on Windows Subsystem for Linux (WSL), its background, and aspects of how it translates Linux system calls through the Windows NT kernel. The article also mentions reproducibly setting up a Windows machine. ### Source excerpt I recently started a job at Microsoft. In my first week I have already learned so much about Windows, I figured I would try to put it all into writing. This post is coming to you from a Windows Subsystem for Linux console! I'm headed to Seattle because I'M JOINING MICROSOFT, at the airport wearing this awesome shirt from @listonb & @Taylorb_msft ���� pic.twitter.com/8rnAg1dsPd -- jessie frazelle (@jessfraz) September 4, 2017 New job and I got a Windows computer and a Linux computer! If you are new to my blog, let me tell you: I love setting up a perfect desktop experience. I've written a few posts on it (for Linux), you should check them out. Setting up a Windows computer is something I have not done in quite some time. I will describe a bit how to set up a windows machine in a reproducible way at the end of this post. I would like to thank Rich Turner, John Starks, Taylor Brown, and Sarah Cooley for taking the time to explain a lot of the following to me. :) Windows Subsystem for Linux (WSL) Let's start with Windows Subsystem for Linux, aka WSL. Even @monkchips wrote that since I joined Microsoft "Linux Subsystem for Windows will definitely be getting a workout." I am super excited about Windows Subsystem for Linux. It is one of the coolest pieces of tech I've seen since I started using Docker. First, a little background on how WSL works... You can learn a lot more about this from the Windows Subsystem for Linux Overview. I will go over some of the parts I found to be the most interesting. The Windows NT kernel was designed from the beginning to support running POSIX, OS/2, and other subsystems. In the early days, these were just user-mode programs that would interact with ntdll to perform system calls. Since the Windows NT kernel supported POSIX there was already a fork system call implemented in the kernel. However, the Windows NT call for fork, NtCreateProcess, is not directly compatible with the Linux syscall so it has some special handling you can read about more