All articles

Switching From Windows to Linux: How It Works in Practice

Switching From Windows to Linux: How It Works in Practice

Under my Linux videos people most often ask not "why" but "how": how exactly the switch from Windows to Linux happens, what you'll run into and what will surprise you. I covered the reasons I left Windows in detail in the article why I switched from Windows to Linux. This one is about the process itself: which distributions I tried, where I went wrong, how the software question got solved and what to do after installing.

Briefly, what pushed me

Three things that built up over years on Windows:

  • Forced updates. They started at the worst possible moment and sometimes even broke the system. On Linux I decide when to update myself: the whole system or a single program, with one command or through a graphical interface. You can even skip updates for years — it's your choice and your responsibility.
  • Micro-freezes. Search, Control Panel and Explorer regularly hung. When you move around the system quickly all day and spend hours chasing a bug, every such freeze drives you mad. Meanwhile Linux in a virtual machine felt noticeably more responsive than Windows on real hardware.
  • Control. Bundled browsers and programs you have to disable by hand, services, startup items, reports sent to Microsoft's servers. Even installing Windows in a VM for a test means disabling the extras first, then activating it — otherwise you can't even change the wallpaper — and then fighting update errors.

On Linux you can choose or replace everything: the kernel, the init system, the bootloader, the file manager, the set of libraries — and customize every part.

Step one: virtual machines

I started by testing in virtual machines: Debian, Ubuntu, Linux Mint. That's the safest way: your main system stays in place, and you calmly learn the terminal, packages and the filesystem. Broke something — roll back a snapshot or recreate the machine.

The mistake: Debian as my first main system

When I decided to switch completely, for some reason I chose Debian. That was a mistake: it's hard for a beginner. I had to figure out how to add repositories in sources.list, how to install drivers, why the version of a program I needed wasn't in the stable branch.

But I sorted it all out, set up the Xfce environment and installed all the programs I needed. The system worked just like Windows, with a bonus — it was very fast: in six months I didn't see a single freeze. I was learning programming at the same time, and knowing Linux noticeably accelerated that growth.

Manjaro and GNOME, then Arch and BSPWM

After Debian I moved to Manjaro with GNOME and spent several years on it. For beginners I'd recommend starting with something like that: Manjaro, Pop!_OS or Linux Mint — a lot works out of the box there.

Over time I got bored with Manjaro: I wanted even more flexibility. I moved to Arch Linux with my own setup on the BSPWM tiling window manager. Now every bar and program does exactly what I need, and navigating the system has become much faster.

Why do programmers so often move to window managers? In regular desktop environments you minimize and restore windows with the mouse or Alt+Tab. In a tiling manager programs arrange themselves into areas of the screen, and switching, moving, closing and launching are done from the keyboard without touching the mouse at all. In routine work that's a big speedup. And constantly tuning your own setup is a great way to level up your knowledge of Linux and programming.

What about software

Development. No problems at all here: Sublime Text, VS Code, Firefox, Chromium, VeraCrypt, VirtualBox, FileZilla and almost every other tool are in the official repositories. You can work with .NET on Linux — I've seen people write .NET code paired with Neovim, and in college I worked with .NET in Rider, which is also available on Linux.

Video and photo. On Windows I edited in Premiere Pro. Now I edit all my videos in Kdenlive, and for more serious work there's DaVinci Resolve. Instead of Photoshop, Krita, GIMP with plugins or the online editor Photopea are enough for me — my thumbnails are simple.

Windows programs. Many of them run through Wine and its front-ends — I tested games, Photoshop and a few other programs. But the system is where you spend the whole day, and Photoshop is just one program. Judging a system by one program isn't right.

What surprised me

  • Speed. Even Debian at the start felt faster than the Windows I was used to.
  • Freedom to customize. You can tune not just the desktop theme but individual widgets inside programs.
  • The system doesn't get in the way. No warnings on a "Hello, world" built with PyInstaller, no activation just to change the wallpaper. Install it — and get to work.
  • Responsibility is yours. If the system breaks after your actions, it's not a corporation's fault but yours. I like that: I'd rather answer for my own decisions than fix someone else's.

What to think about before installing

  • A backup. Before partitioning the disk, save your important data separately: a mistake in the installer costs more than half an hour spent on a backup.
  • Dual boot. If you keep Windows alongside, keep in mind that its major updates sometimes change the bootloader, and enabled BitLocker will require a recovery key. Better to find the key in advance.
  • Hardware. Check how the distribution works with your graphics card and Wi-Fi: the easiest way is to boot it from a USB stick in live mode without installing anything.

How to switch if you're a developer

  1. Start with a virtual machine. Get comfortable with the terminal, the package manager and the filesystem layout.
  2. Pick a friendly distribution: Linux Mint, Pop!_OS, Ubuntu or Manjaro. Leave Debian and Arch for later.
  3. Install it as a second system (dual boot) once you're confident with the basics, then switch completely.
  4. Check your programs in advance: whether they're in the repositories, whether there are native alternatives, whether they run through Wine.
  5. After installing, make the system your own: icons, themes, the desktop environment. Every such step teaches you something new about Linux.

If you mostly use your computer for a browser and YouTube, the switch will be almost unnoticeable. For programmers it's also a strong boost to growth. Once you've settled in, start with 10 useful Linux programs, and if you want to get more out of old hardware, see the article on CachyOS. Where I eventually ended up after Arch is covered in NixOS after Arch Linux.

Sources