Starting from a Windows development machine with an NVIDIA GPU, this article explains how to verify CUDA in WSL, run a small PyTorch test, place local model caches, and debug cases where the GPU is not actually being used.
A practical migration note for a mixed Python and Node project: move the repository from a Windows partition into the WSL Linux filesystem, then redraw the boundaries around files, paths, process calls, and performance.
Starting from a nearly full C drive, this article explains why WSL2 ext4.vhdx files grow but do not immediately shrink, how to locate Docker, node_modules, model caches, and package caches, and how to clean and compact them safely.
Using a local API service as the example, this article explains Docker Desktop's WSL backend, bind mounts, named volumes, hot reload, logs, and disk-space hygiene.
Starting from a team development-environment migration, this article explains the boundaries of WSL1, WSL2, distributions, VHDX storage, Windows integration, systemd, networking, and filesystems, so you can decide what belongs in WSL.
Using a small image batch-processing utility as the thread, this article explains Qt, GTK, and OpenCV GUI development under WSLg, including environment checks, debugging, file boundaries, packaging choices, and team usage.
Using a real log investigation and batch file-cleanup workflow, this article explains how to connect rg, jq, awk, fzf, make, timers, editors, and Windows tools into a stable WSL-based workflow.
Starting from xeyes, gedit, and remote windows, this article explains the roles of X11, Wayland, XWayland, Weston, and RDP inside WSLg, and why old DISPLAY-based tutorials can now be counterproductive.
Starting from a simple fim image.png command, this article explains why WSLg can display Linux GUI programs directly on the Windows desktop, and how that helps with image previews, computer-vision work, and small X11 tools.
9 published posts are not listed in the outline.