<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rouwel Ngacha</title>
    <description>The latest articles on DEV Community by Rouwel Ngacha (@rrouwelng).</description>
    <link>https://dev.to/rrouwelng</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3924978%2F2d5c38e4-653e-4d1b-8628-91c93c7fd86c.png</url>
      <title>DEV Community: Rouwel Ngacha</title>
      <link>https://dev.to/rrouwelng</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rrouwelng"/>
    <language>en</language>
    <item>
      <title>Use MangoHud to Diagnose Linux Game Performance, Not Just Show FPS</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 22:16:12 +0000</pubDate>
      <link>https://dev.to/rrouwelng/use-mangohud-to-diagnose-linux-game-performance-not-just-show-fps-162d</link>
      <guid>https://dev.to/rrouwelng/use-mangohud-to-diagnose-linux-game-performance-not-just-show-fps-162d</guid>
      <description>&lt;p&gt;When a game feels slow, the first instinct is often to look for a single FPS number. That number is useful, but it does not explain why the game feels bad. Linux gamers can use MangoHud, an open-source overlay for Vulkan and OpenGL applications, to observe frame rate, frame times, CPU and GPU load, temperatures, and other metrics.&lt;/p&gt;

&lt;p&gt;The goal is not to cover the screen with numbers. It is to use a few measurements to answer a specific question: Is the game limited by the GPU? Is frame delivery uneven? Is the CPU saturated? Is the system overheating or simply waiting on a shader compilation? MangoHud can help collect clues, but it cannot diagnose every cause automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  What MangoHud displays
&lt;/h2&gt;

&lt;p&gt;MangoHud is an overlay that can show performance information while a game runs. Its project documentation lists data such as FPS, frame-time information, CPU and GPU usage, and temperatures. The exact metrics available depend on hardware, drivers, permissions, and the installed build.&lt;/p&gt;

&lt;p&gt;On Fedora, for example, the project’s current README documents installation through the distribution package manager with &lt;code&gt;sudo dnf install mangohud&lt;/code&gt;. Other distributions use their own package names and repositories. If you use Steam as a Flatpak, there is a Flatpak runtime extension for MangoHud, and the setup differs from a system package. Follow the instructions for the Steam packaging method you actually use.&lt;/p&gt;

&lt;p&gt;For a normal Steam game on a system-installed build, the basic launch option is commonly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mangohud %command%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For some setups, an environment variable can also enable the layer, but the project notes differences between Vulkan, OpenGL, Gamescope, and Flatpak configurations. Start with the documentation for your build rather than assuming one command works everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read frame time, not only FPS
&lt;/h2&gt;

&lt;p&gt;FPS is the number of frames presented per second over a period. Frame time measures how long each frame takes. At 60 FPS, the average frame interval is about 16.7 milliseconds. At 30 FPS, it is about 33.3 milliseconds. These averages do not show whether individual frames arrive evenly.&lt;/p&gt;

&lt;p&gt;A game can report a high average FPS while producing occasional long frames that look like stutter. A frame-time graph can reveal spikes that the average hides. If the graph is mostly consistent and then spikes during a new area or effect, shader compilation or asset streaming may be involved. If the frame times remain high throughout a scene, the game may be under sustained CPU or GPU load.&lt;/p&gt;

&lt;p&gt;When comparing settings, use the same reproducible segment. A busy city, menu, and empty corridor can put different loads on the system. Record the same route or benchmark, use the same resolution and graphics settings, and compare more than a short moment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use CPU and GPU load as clues
&lt;/h2&gt;

&lt;p&gt;If the GPU stays near full utilization while the frame rate is below your target, the game may be GPU-bound. Reducing resolution or expensive graphics settings can test that theory. If GPU use is low while one or more CPU cores are heavily loaded, the game may be CPU-bound or waiting on another part of the system.&lt;/p&gt;

&lt;p&gt;These indicators are not absolute. Some games distribute work unevenly across CPU cores. Driver overhead, synchronization, storage stalls, and frame caps can all make utilization look lower than expected. A game capped at 60 FPS may not use the GPU fully because it does not need to. Low usage is not automatically evidence of a broken driver.&lt;/p&gt;

&lt;p&gt;Temperatures and clock speeds add context. If performance drops after several minutes while temperatures rise, thermal or power limits may be involved. But a high temperature by itself is not a diagnosis. Compare the behavior to the device’s expected operating range and check system logs or vendor guidance before changing fan curves or power limits.&lt;/p&gt;

&lt;h2&gt;
  
  
  A repeatable measurement workflow
&lt;/h2&gt;

&lt;p&gt;Start with one question. For example: “Does lowering the resolution improve performance?” Launch the game with the same scene and collect a baseline. Change the resolution only, repeat the scene, and compare frame-time consistency, average FPS, GPU load, and temperature.&lt;/p&gt;

&lt;p&gt;Then test another variable if needed. If lowering resolution changes little, the GPU may not be the limiting factor. Try a graphics setting that affects CPU or GPU work, or check whether the game’s frame limiter is active. Change one thing at a time and write down the result.&lt;/p&gt;

&lt;p&gt;A useful note might read: “In the same 90-second route, 1440p medium averages 54 FPS with repeated 30–40 ms spikes; 1080p medium averages 56 FPS with similar spikes; GPU use falls from 97% to 72%.” This suggests that resolution was not the only factor, though more investigation is needed. It is more actionable than “performance feels bad.”&lt;/p&gt;

&lt;h2&gt;
  
  
  Common measurement traps
&lt;/h2&gt;

&lt;p&gt;Do not compare one run with shader caches warmed against another first launch without noting the difference. Shader compilation can create temporary stutter, and the behavior may change on a later run. Similarly, background updates, browser tabs, recording software, and overlays can affect results.&lt;/p&gt;

&lt;p&gt;A frame cap changes utilization. If a game is capped, a GPU may sit below full load by design. Disable or account for V-sync, in-game limiters, driver-level caps, Gamescope limits, and refresh rate when interpreting results. Multiple overlays or capture tools can also interfere with one another.&lt;/p&gt;

&lt;p&gt;Overlay data may be incomplete. Some sensors require additional permissions or libraries. A missing temperature reading does not mean the GPU has no temperature sensor; it may mean the overlay cannot access it. Do not run the entire game as root to make an overlay show a metric.&lt;/p&gt;

&lt;h2&gt;
  
  
  Gamescope and MangoHud
&lt;/h2&gt;

&lt;p&gt;Gamescope can run a game in a nested compositor, and MangoHud can display telemetry. The projects have a specific integration path: MangoHud’s documentation indicates using &lt;code&gt;mangoapp&lt;/code&gt; with Gamescope when appropriate, rather than assuming the ordinary MangoHud injection works in every Gamescope configuration. Check current project documentation and distro packaging because options evolve.&lt;/p&gt;

&lt;p&gt;Avoid piling Gamescope, MangoHud, multiple frame limiters, and launch variables into a single command before testing each component. First confirm the game works. Then enable the overlay by itself. Add Gamescope separately if you need its scaling or window behavior. This isolates errors and makes results easier to interpret.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to share a performance report
&lt;/h2&gt;

&lt;p&gt;Include hardware, distribution, kernel and graphics driver versions, game version, Proton version if applicable, resolution, settings, frame cap, and the scene tested. Note whether the figures are from a cold or warmed-up run. If you post screenshots, remove usernames or other private information visible in the overlay or desktop.&lt;/p&gt;

&lt;p&gt;MangoHud is not a benchmark suite and its metrics do not tell the whole story. Input latency, display refresh, frame pacing, game engine behavior, and subjective smoothness still matter. Use the overlay to support a controlled comparison, not to chase a single number.&lt;/p&gt;

&lt;p&gt;A good performance investigation starts with a question, collects measurements under repeatable conditions, and changes one setting at a time. MangoHud makes more of the system visible while you play. The real skill is interpreting those signals carefully enough to know which layer to test next.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/flightlessmango/MangoHud" rel="noopener noreferrer"&gt;MangoHud project and documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/gamescope" rel="noopener noreferrer"&gt;ValveSoftware/Gamescope on GitHub&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.mesa3d.org/drivers/radv.html" rel="noopener noreferrer"&gt;Mesa RADV documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>performance</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Your First Windows Game on Linux: A Practical Steam Proton Setup</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 22:14:12 +0000</pubDate>
      <link>https://dev.to/rrouwelng/your-first-windows-game-on-linux-a-practical-steam-proton-setup-55eo</link>
      <guid>https://dev.to/rrouwelng/your-first-windows-game-on-linux-a-practical-steam-proton-setup-55eo</guid>
      <description>&lt;p&gt;One of the most surprising parts of modern Linux gaming is that a Windows-only Steam game may launch without a Windows installation. Steam’s compatibility tool, Proton, makes that possible for many titles. The basic setup is often simple, but a few good habits can save you from confusing troubleshooting later.&lt;/p&gt;

&lt;p&gt;This guide walks through a cautious first run: install Steam from a trusted source, use the default compatibility setting, test one game, and only then investigate alternatives. Menu names can move between Steam versions and distributions, so treat the instructions as a route rather than an exact screenshot-by-screenshot promise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you install anything
&lt;/h2&gt;

&lt;p&gt;First, make sure your Linux distribution is current and that the graphics driver appropriate for your hardware is installed through the distribution’s recommended method. Proton relies on the host system’s graphics stack. A game can fail to start if Vulkan or required 32-bit graphics components are missing, even if the game itself and Proton are installed correctly.&lt;/p&gt;

&lt;p&gt;Install Steam from your distribution’s supported software source or Valve’s official distribution guidance. Avoid third-party installer bundles unless you understand how they are maintained. If your Steam client is packaged as a Flatpak, its filesystem permissions and runtime environment are part of the setup; do not assume its paths and tools are identical to a traditional system package.&lt;/p&gt;

&lt;p&gt;You will also need enough storage. Many modern games are large, and Proton creates per-game compatibility data in addition to the game files. If you plan to put a Steam library on a separate disk, configure the library through Steam rather than copying an old Windows library folder and assuming it will behave the same on Linux.&lt;/p&gt;

&lt;h2&gt;
  
  
  Enable Steam Play where needed
&lt;/h2&gt;

&lt;p&gt;Open Steam and sign in. In the client settings, find the Compatibility or Steam Play section. Many titles that Valve has tested can use Proton automatically. To allow Proton for other Windows games, enable the option to use Steam Play for all titles, then restart Steam if the client asks you to.&lt;/p&gt;

&lt;p&gt;The exact wording varies by client release. The important concept is that Steam can select Proton for a Windows game. Enabling it does not promise every title will work. It makes Proton available as the compatibility tool.&lt;/p&gt;

&lt;p&gt;Valve’s Proton project recommends that most users start with the Proton version provided by Steam itself. The client receives versions of Proton that it can manage and present in each game’s compatibility settings. You usually do not need to download Proton separately or build it from source.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose a first test game
&lt;/h2&gt;

&lt;p&gt;Pick a game with recent reports of successful play and no known platform-specific anti-cheat block. A single-player game is a less frustrating first test than a competitive title that requires online services. ProtonDB can help you inspect user reports, but remember that the reports vary by date, hardware, and game version.&lt;/p&gt;

&lt;p&gt;Install the game normally in Steam and press Play. On a first launch, Steam may download a Proton version and prepare compatibility data. This can take longer than a native Linux game’s first start. Let that process finish before deciding that the launch has stalled.&lt;/p&gt;

&lt;p&gt;If the game opens, play for more than a minute. Test the main menu, a save or tutorial, audio, controller or keyboard input, and any important video. A launcher appearing does not prove that the whole game is playable. If you mainly care about multiplayer, confirm that online matchmaking works rather than assuming that a successful offline launch means all services work.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you need to select a different Proton version
&lt;/h2&gt;

&lt;p&gt;For an individual game, open its Properties in your Steam library and look for Compatibility. You can force the use of a particular Steam Play compatibility tool there. The default is the right starting point for most games; changing versions is a troubleshooting experiment.&lt;/p&gt;

&lt;p&gt;A newer version may contain a fix for a recent game update, while an older version may avoid a regression. The version number alone does not tell you which one will work best. Check recent reports for the title and try one change at a time. If switching versions does not help, revert to the previous choice rather than leaving an unexplained override in place.&lt;/p&gt;

&lt;p&gt;Community-maintained Proton builds sometimes include additional changes. They can be useful for specific cases, but they are not a requirement for a normal Steam setup and do not guarantee success. Prefer official versions first, and get community builds only from a source you trust.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens to game data?
&lt;/h2&gt;

&lt;p&gt;Proton uses a Wine prefix for a game. In broad terms, this is a per-game directory that contains Windows-like configuration and files needed by the compatibility environment. Steam stores Proton compatibility data associated with the game’s app ID. The exact location depends on where your Steam library is installed.&lt;/p&gt;

&lt;p&gt;That prefix may contain settings and saves that are not synchronized by Steam Cloud. Do not delete compatibility data as a first troubleshooting step unless you have checked whether important local data is backed up. The prefix is not merely disposable cache. Some games keep local saves or configuration there.&lt;/p&gt;

&lt;p&gt;If you remove and reinstall a game, Steam’s behavior for the game installation and compatibility data can depend on your actions and client version. Treat any manual deletion under &lt;code&gt;steamapps/compatdata&lt;/code&gt; as a potentially destructive operation. Back up saves you care about and confirm the app ID before altering a directory.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple troubleshooting order
&lt;/h2&gt;

&lt;p&gt;If the game fails, record what happens. Does Steam show “Running” and then stop? Does a launcher appear? Is there an error message? Does the game reach a menu but fail when joining a server? These are distinct problems.&lt;/p&gt;

&lt;p&gt;Next, verify the game files through Steam. Check the distribution’s support pages for Steam and Vulkan. Look at recent ProtonDB reports and the game publisher’s support notes. Then try another official Proton version if evidence suggests it may help. Avoid adding launch options copied from a random discussion until you know what they do.&lt;/p&gt;

&lt;p&gt;For a Proton debug log, Valve’s Proton FAQ describes adding &lt;code&gt;PROTON_LOG=1 %command%&lt;/code&gt; to the game’s Steam launch options. The log is written in your home directory with the game’s Steam app ID in its name. Logs can contain usernames, local paths, and other system details, so review and redact them before posting publicly. Remove the option after gathering the log so it does not create unnecessary files on every launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep expectations realistic
&lt;/h2&gt;

&lt;p&gt;Proton provides a convenient compatibility path; it is not a guarantee that every Windows game will run. A title may be blocked by anti-cheat or publisher policy, depend on a difficult launcher, or have a regression after an update. This is not usually fixed by reinstalling the entire operating system.&lt;/p&gt;

&lt;p&gt;A reliable first-time approach is deliberately boring: use supported drivers, enable Steam Play, choose a game with current positive reports, launch it with the default Proton version, and test the features you care about. If something fails, change one variable and take notes. That method produces a working setup more often than collecting tweaks before the first launch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/Proton" rel="noopener noreferrer"&gt;ValveSoftware/Proton project&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ" rel="noopener noreferrer"&gt;Valve Proton FAQ: logging and prefixes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.protondb.com/" rel="noopener noreferrer"&gt;ProtonDB&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>steam</category>
      <category>beginners</category>
    </item>
    <item>
      <title>DNF and Flathub: Two Different Ways to Install Apps on Linux</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:57:57 +0000</pubDate>
      <link>https://dev.to/rrouwelng/dnf-and-flathub-two-different-ways-to-install-apps-on-linux-d9</link>
      <guid>https://dev.to/rrouwelng/dnf-and-flathub-two-different-ways-to-install-apps-on-linux-d9</guid>
      <description>&lt;p&gt;When people move to Linux, one of the first questions they ask is: “Where do I download software?” On Windows, the answer is often a website or the Microsoft Store. On Linux, there are several ways to install applications, and two common options on Fedora are DNF and Flatpak apps from Flathub.&lt;/p&gt;

&lt;p&gt;These options are not simply two storefronts competing to do the same thing. They represent different approaches to software distribution. Understanding the difference helps you choose the right source, diagnose dependency issues, and avoid the mistaken idea that every Linux app must be installed in exactly the same way.&lt;/p&gt;

&lt;h2&gt;
  
  
  DNF: your distribution’s package manager
&lt;/h2&gt;

&lt;p&gt;DNF is Fedora’s package manager for installing, updating, and removing system packages. It obtains packages from configured software repositories, checks their dependencies, and performs the required changes as a transaction. Fedora’s current releases use DNF5 by default, though some older documentation and systems may still refer to the earlier DNF implementation. &lt;a href="https://docs.fedoraproject.org/en-US/quick-docs/dnf/" rel="noopener noreferrer"&gt;Fedora’s DNF documentation&lt;/a&gt; describes the everyday workflow.&lt;/p&gt;

&lt;p&gt;A typical command-line workflow looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Search package metadata&lt;/span&gt;
sudo dnf search package-name

&lt;span class="c"&gt;# Install a package&lt;/span&gt;
sudo dnf install package-name

&lt;span class="c"&gt;# Update installed packages&lt;/span&gt;
sudo dnf upgrade

&lt;span class="c"&gt;# Remove a package&lt;/span&gt;
sudo dnf remove package-name
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;DNF is not just a downloader. It resolves dependencies and considers the packages already installed on the system. If an application needs libraries or helper tools, DNF can install those from the repositories as part of the same transaction. That integration is useful for command-line tools, system components, development libraries, and software that should closely match the distribution’s supported environment.&lt;/p&gt;

&lt;p&gt;The tradeoff is that a package is built and maintained for a particular distribution and release. A package available on one Fedora release may not exist in the same form on another distribution. The installed application also generally relies on libraries supplied by the host system. This is a feature when the package is intended to integrate with the OS; it can be an inconvenience when an application needs a newer library than the one in an older distribution.&lt;/p&gt;

&lt;p&gt;DNF commands normally use administrator privileges for system-wide changes. Review the proposed transaction before confirming it, especially when removing packages or accepting a large set of changes. DNF makes dependency handling easier, but it does not make every system modification risk-free.&lt;/p&gt;

&lt;h2&gt;
  
  
  Flatpak and Flathub: application packaging across distributions
&lt;/h2&gt;

&lt;p&gt;Flatpak is an application distribution and sandboxing technology. Flathub is a popular repository, or remote, from which users can install Flatpak applications. An application is identified by an application ID such as &lt;code&gt;org.gimp.GIMP&lt;/code&gt;, rather than only by a package name that varies by distribution.&lt;/p&gt;

&lt;p&gt;Many Flatpak apps use shared runtimes. A runtime supplies common libraries and platform components, while the application package supplies the app itself. Multiple apps can share a runtime, and different runtimes can coexist. This helps an app use a consistent set of libraries across distributions, although it can mean additional downloads and disk use compared with an app that uses libraries already present on the host.&lt;/p&gt;

&lt;p&gt;On Fedora Workstation, Flatpak support is generally installed by default, and Flathub may already be enabled through Fedora’s third-party repository setup. If it is not enabled, Flathub provides Fedora setup instructions. The manual command is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;flatpak remote-add --if-not-exists flathub \
  https://dl.flathub.org/repo/flathub.flatpakrepo
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then search and install by application ID:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;flatpak search gimp
flatpak install flathub org.gimp.GIMP
flatpak run org.gimp.GIMP
flatpak update
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can also use GNOME Software or KDE Discover, which can present Flatpak apps alongside other software sources. When the same app appears from multiple sources, check which source you are installing from.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does the sandbox actually mean?
&lt;/h2&gt;

&lt;p&gt;Flatpak applications run with restricted access to parts of the host system. An app may receive access to particular files, devices, or services that it needs. The exact permissions depend on the application’s packaging and configuration. Sandboxing can reduce unnecessary access, but it is not a guarantee that every Flatpak is perfectly isolated or that an app cannot access anything sensitive.&lt;/p&gt;

&lt;p&gt;For example, a video editor may need access to folders containing media. A game launcher may need access to a library directory. Depending on how those permissions are configured, the app might not see a folder you can access in your regular desktop session. This can look like a broken installation when it is actually a permission boundary.&lt;/p&gt;

&lt;p&gt;Inspect permissions with tools such as Flatseal, or from the command line with &lt;code&gt;flatpak info --show-permissions APP_ID&lt;/code&gt;. Change permissions only when you understand why the application needs access. Granting broad access to the entire home directory can solve a short-term inconvenience while weakening the purpose of the sandbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which option should I choose?
&lt;/h2&gt;

&lt;p&gt;Use DNF when you are installing system tools, development packages, command-line utilities, drivers or components that need tight integration with Fedora. It is also the natural choice when Fedora’s repositories are the intended source and you want the distribution to manage updates with the rest of the OS.&lt;/p&gt;

&lt;p&gt;Use Flatpak when the software is distributed on Flathub, you want a broadly compatible desktop application, or you need an application that can use a different runtime from the host. Flatpak is especially common for desktop apps such as media tools, chat clients, and creative software.&lt;/p&gt;

&lt;p&gt;There is no universal rule that one format is safer or better. The package source and maintainer matter. Prefer official distribution repositories or the application publisher’s verified source. On Flathub, check the publisher information and app details. A package manager can deliver an outdated or poorly maintained app; a sandboxed app can still request powerful permissions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can both be installed at once?
&lt;/h2&gt;

&lt;p&gt;Yes. A system can have both DNF packages and Flatpak apps. In some cases you may even find the same application in both places. That can be useful, but it can also be confusing: each copy may store settings differently, use a different version, and have separate update channels.&lt;/p&gt;

&lt;p&gt;If you encounter duplicated launchers, check the app’s source in your software center or list installed apps using &lt;code&gt;dnf list installed&lt;/code&gt; and &lt;code&gt;flatpak list&lt;/code&gt;. If you choose to switch formats, remove the copy you no longer want and check whether you need to preserve or migrate its settings and data first.&lt;/p&gt;

&lt;p&gt;The simplest mental model is this: DNF manages software packages as part of Fedora’s system environment; Flatpak distributes desktop apps with runtimes and permission boundaries that work across distributions; and Flathub is one important source of Flatpak applications. Once you know which layer you are using, choosing and troubleshooting Linux software becomes much less mysterious.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.fedoraproject.org/en-US/quick-docs/dnf/" rel="noopener noreferrer"&gt;Fedora: Using the DNF software package manager&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.fedoraproject.org/en-US/quick-docs/flathub-flatpak-applications/" rel="noopener noreferrer"&gt;Fedora: Installing Flatpak applications from Flathub&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://flathub.org/en/setup/Fedora" rel="noopener noreferrer"&gt;Flathub setup for Fedora&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>fedora</category>
      <category>opensource</category>
      <category>beginners</category>
    </item>
    <item>
      <title>How Wine and Proton Make Windows Games Run on Linux</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:57:47 +0000</pubDate>
      <link>https://dev.to/rrouwelng/how-wine-and-proton-make-windows-games-run-on-linux-44fi</link>
      <guid>https://dev.to/rrouwelng/how-wine-and-proton-make-windows-games-run-on-linux-44fi</guid>
      <description>&lt;p&gt;If a Windows game runs on Linux, it is tempting to imagine a tiny copy of Windows hidden inside Steam. Usually, that is not what is happening. Steam’s Proton uses Wine and other compatibility components to implement Windows behavior on Linux. It is not a traditional virtual machine, and the distinction explains both its performance potential and its compatibility limits.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wine is a compatibility layer, not an emulator
&lt;/h2&gt;

&lt;p&gt;Wine’s name stands for “Wine Is Not an Emulator.” Wine implements Windows APIs so that a Windows program can run on a POSIX operating system such as Linux. Instead of booting a separate Windows kernel, Wine handles Windows API calls and maps them to services and behavior available on the host. The Wine project describes this as translating Windows API calls into POSIX calls on the fly. &lt;a href="https://www.winehq.org/" rel="noopener noreferrer"&gt;WineHQ&lt;/a&gt; provides the project overview.&lt;/p&gt;

&lt;p&gt;A Windows application expects a particular environment. It may call functions for files, windows, audio, input, networking, graphics, and other operating-system services. Wine supplies compatible implementations for many of those interfaces. When the application asks Windows for an operation, Wine attempts to provide equivalent behavior through the host system.&lt;/p&gt;

&lt;p&gt;This can avoid the overhead of running a full guest operating system, but it does not mean Wine can automatically run every Windows program. Compatibility depends on whether the APIs and behaviors the application relies on are implemented correctly and whether the app makes assumptions that Wine does not satisfy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Proton packages a gaming-focused stack
&lt;/h2&gt;

&lt;p&gt;Proton is Valve’s compatibility tool for Steam. It is based on Wine and includes additional components and integration intended to make Windows games practical to launch through Steam. Valve describes it as a modified version of Wine combined with high-performance graphics API implementations. &lt;a href="https://partner.steamgames.com/doc/steamhardware/proton" rel="noopener noreferrer"&gt;Valve’s Steamworks Proton documentation&lt;/a&gt; provides a technical overview and information for game developers.&lt;/p&gt;

&lt;p&gt;A particularly important part of the graphics stack is translation between graphics APIs. Many Windows games use Direct3D. Linux graphics drivers commonly expose Vulkan or OpenGL. Proton can use components such as DXVK to translate Direct3D 9, 10, and 11 calls to Vulkan, and vkd3d-proton to translate Direct3D 12 to Vulkan. These translators do not turn the game into a native Linux game. They implement the relevant graphics behavior so the game can communicate with the Linux graphics stack.&lt;/p&gt;

&lt;p&gt;The result is a chain of components: the game makes Windows API and Direct3D calls; Wine and Proton handle Windows-facing behavior; graphics translation maps supported Direct3D functionality to Vulkan; and the host’s Vulkan driver communicates with the GPU. The exact details vary by game, Proton release, hardware, and driver.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can performance be good?
&lt;/h2&gt;

&lt;p&gt;Because Wine is not running a complete guest operating system, it can avoid some overhead associated with virtualization. The game’s code can execute directly on the host CPU, subject to compatibility and translation work. Graphics translation layers also use Vulkan rather than rendering every frame through a slow software fallback.&lt;/p&gt;

&lt;p&gt;That does not guarantee equal or better performance than Windows. Translation and shader compilation have costs. A game may behave differently because of driver implementation, CPU scheduling, shader cache state, or a bug in any layer. Performance is an end-to-end property, not a promise made by the word “compatibility.”&lt;/p&gt;

&lt;p&gt;The first launch may stutter while shaders are compiled or cached. Later launches can improve, but this depends on the game and driver. If performance changes after a driver or Proton update, that does not necessarily mean the hardware became slower; a change in a compatibility component may have altered the workload or exposed a regression.&lt;/p&gt;

&lt;h2&gt;
  
  
  The prefix: a per-game Windows-like environment
&lt;/h2&gt;

&lt;p&gt;Wine uses a prefix, a directory containing configuration and files that imitate parts of a Windows environment. Proton typically manages prefixes for Steam games. Each title can have its own prefix so its settings and installed components do not automatically collide with those of another title.&lt;/p&gt;

&lt;p&gt;That isolation is useful when one game needs a particular configuration. It also means that deleting a prefix can delete the game’s Windows-side settings, registry data, and local files stored there. It is not the same thing as uninstalling and reinstalling the whole Linux system. Before deleting a prefix, back up saves or configuration that are not synced to the cloud and that matter to you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Proton does not solve automatically
&lt;/h2&gt;

&lt;p&gt;A game can fail even when its graphics APIs are supported. It may depend on a launcher, DRM component, video codec, unusual Windows behavior, or an anti-cheat system. The game publisher may also change its launcher or server-side checks after a previously successful release.&lt;/p&gt;

&lt;p&gt;Anti-cheat deserves special attention. Some user-space anti-cheat systems can be configured by developers to work with Proton, but compatibility is not automatic. Valve’s developer documentation says Easy Anti-Cheat and BattlEye can be supported with additional title-specific setup. Kernel-level anti-cheat is a different challenge and is not generally supported in the same way. The game’s developer and anti-cheat provider need to enable the relevant path.&lt;/p&gt;

&lt;p&gt;That distinction matters because “Proton supports this anti-cheat” does not mean “every game using it works.” A game may use the same vendor’s technology but have different configuration, server settings, or anti-cheat components.&lt;/p&gt;

&lt;h2&gt;
  
  
  Picking a Proton version
&lt;/h2&gt;

&lt;p&gt;For most users, start with the Proton version Steam selects by default. The Proton project recommends using the version provided by the Steam client. If a title has a problem, you can try another version through the game’s Steam Properties under Compatibility. This is a diagnostic step, not a universal upgrade path: a newer version can fix one issue and introduce another.&lt;/p&gt;

&lt;p&gt;Community builds can include additional patches or newer components, but they are not an official guarantee of compatibility. Use them only when you understand how to select and remove them, and prefer trusted sources. A setting copied from a forum can affect a game in unexpected ways. Change one variable at a time so you can tell what actually helped.&lt;/p&gt;

&lt;h2&gt;
  
  
  A useful troubleshooting sequence
&lt;/h2&gt;

&lt;p&gt;First, confirm that the title is intended to launch through Steam and that the game files are intact. Check recent reports for the current release and your platform. Try the default Proton version before applying launch flags. If the game fails after an update, test a different official Proton release and note whether the result changes.&lt;/p&gt;

&lt;p&gt;When you report a problem, include the game name, operating system, GPU and driver, Proton version, symptoms, and any steps that reproduce the issue. “It crashes” is much harder to investigate than “the game reaches the publisher logo, then exits before the main menu after the latest patch.”&lt;/p&gt;

&lt;p&gt;Wine and Proton are impressive because they provide compatibility without turning every launch into a virtualized Windows session. But the system is a stack of implementations, and the game only works when the relevant parts of that stack line up. Knowing the roles of Wine, Proton, graphics translation, drivers, and game-side services turns a vague compatibility question into a solvable debugging problem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.winehq.org/" rel="noopener noreferrer"&gt;WineHQ: What is Wine?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://partner.steamgames.com/doc/steamhardware/proton" rel="noopener noreferrer"&gt;Valve Steamworks: Steam Hardware and Proton&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/Proton" rel="noopener noreferrer"&gt;ValveSoftware/Proton on GitHub&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Virtual Machines and Gaming: What VMware Is Really Doing</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:57:36 +0000</pubDate>
      <link>https://dev.to/rrouwelng/virtual-machines-and-gaming-what-vmware-is-really-doing-448n</link>
      <guid>https://dev.to/rrouwelng/virtual-machines-and-gaming-what-vmware-is-really-doing-448n</guid>
      <description>&lt;p&gt;Virtual machines are often described as “a computer inside your computer.” That phrase is useful as a first approximation, but it hides the key question for gaming: which hardware does the virtual machine actually receive?&lt;/p&gt;

&lt;p&gt;A VM can run another operating system in a window, but it does not automatically have a direct connection to the host’s graphics card. That difference separates a convenient desktop VM from a setup capable of demanding 3D gaming.&lt;/p&gt;

&lt;h2&gt;
  
  
  The hypervisor and the guest
&lt;/h2&gt;

&lt;p&gt;A virtual machine is a software-defined computer created by a hypervisor. It has virtual CPUs, memory, storage, network devices, and display hardware. The guest operating system sees those devices and loads drivers for them. VMware Workstation is a hosted hypervisor: it runs as an application on a host operating system and relies on the host to manage the physical computer.&lt;/p&gt;

&lt;p&gt;Modern processors provide hardware virtualization features that help a hypervisor run guest code efficiently. The guest still believes it has a CPU and operating system of its own, but the hypervisor controls how the guest accesses the physical resources. Memory is mapped between guest and host, virtual disks are backed by files or devices, and virtual networking connects the guest to the host or network.&lt;/p&gt;

&lt;p&gt;A guest operating system is not simply a process. It has its own kernel and system services, isolated from the host within the limits of the hypervisor and configuration. This is why you can install a separate Windows or Linux operating system in a VM without replacing the host.&lt;/p&gt;

&lt;h2&gt;
  
  
  The GPU is the gaming bottleneck
&lt;/h2&gt;

&lt;p&gt;A VM’s virtual display adapter is not necessarily the physical GPU. In a typical desktop VM, the hypervisor exposes a virtual graphics device and provides 3D acceleration by forwarding or translating graphics work through a host-side driver. This can be perfectly adequate for desktop effects, development, and lightweight 3D. It may not deliver the same feature set or performance as the GPU being used directly by a native game.&lt;/p&gt;

&lt;p&gt;A Windows game might query the GPU for Direct3D features, shader-model support, memory, or driver behavior. If the virtual adapter exposes a reduced or different capability set, the game may refuse to launch, show errors, or run poorly. A large amount of RAM and many virtual CPU cores cannot compensate for a GPU path that lacks the required capabilities.&lt;/p&gt;

&lt;p&gt;VMware’s virtual graphics path has changed over time and varies across products, host systems, and releases. Always check the current product documentation for supported guest operating systems and graphics features rather than relying on an old tutorial that may describe a different version.&lt;/p&gt;

&lt;h2&gt;
  
  
  GPU passthrough is a different design
&lt;/h2&gt;

&lt;p&gt;GPU passthrough assigns a physical GPU, or a supported virtual GPU partition, to a guest. The guest can then use a driver intended for that device. This can provide much closer access to GPU performance, but it is not the default behavior of an ordinary desktop VM.&lt;/p&gt;

&lt;p&gt;Passthrough requires compatible hardware, firmware, hypervisor support, and configuration. The GPU must be isolated and available to the guest. On a single-GPU desktop, handing the GPU to the VM can make it unavailable to the host while the guest is running. Many setups therefore use a second GPU or integrated graphics for the host. Some commercial vGPU features also require specific supported hardware and licensing.&lt;/p&gt;

&lt;p&gt;A virtual GPU and full device passthrough are not interchangeable terms. A virtual GPU can divide or expose GPU resources through a supported virtualization stack. Passthrough gives a device to the guest more directly. Each has different requirements, isolation characteristics, supported products, and performance behavior.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why use a VM for games at all?
&lt;/h2&gt;

&lt;p&gt;There are valid reasons to try gaming in a VM. You may need to test a game on a specific operating system, keep a work environment separate, use software that is unavailable on the host, or run an older title that expects a particular Windows environment. A VM also makes snapshots and disposable test environments practical.&lt;/p&gt;

&lt;p&gt;But if the aim is simply “play a Windows Steam game on Linux,” a compatibility layer such as Proton may be simpler than installing Windows into a VM. Proton runs within the host environment rather than requiring a second operating system and a gaming-capable virtual graphics configuration. It has its own compatibility limits, but it avoids the common assumption that a VM automatically provides access to the full GPU.&lt;/p&gt;

&lt;h2&gt;
  
  
  VMware versus KVM is not the main question
&lt;/h2&gt;

&lt;p&gt;People often ask whether VMware or another hypervisor is best for gaming. The answer depends on the host, guest, hardware, product edition, and passthrough support. The first question should be: what graphics device does the guest see, and does the hypervisor officially support the features your game requires?&lt;/p&gt;

&lt;p&gt;Check the guest’s reported adapter and feature levels. Confirm whether 3D acceleration is enabled and which API versions are available. Review the current hypervisor release notes. If a game uses anti-cheat, check whether running it inside a VM is permitted and supported by the game publisher. Some security systems intentionally reject virtualized environments, and bypassing those checks may violate terms or trigger account sanctions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical expectations
&lt;/h2&gt;

&lt;p&gt;For office apps, software testing, and general desktop use, VMware Workstation can provide a convenient virtual environment. For graphics-intensive gaming, the default virtual adapter may be the limiting factor. For near-native gaming performance, GPU passthrough or supported vGPU solutions may be necessary, but they add hardware and setup complexity.&lt;/p&gt;

&lt;p&gt;If you are experimenting, begin with a non-critical VM and a game that does not depend on strict anti-cheat checks. Measure performance rather than relying on the VM’s assigned CPU count. Check temperature, host load, frame pacing, and the guest’s graphics capabilities. Keep the host and guest drivers up to date, but avoid changing several variables at once.&lt;/p&gt;

&lt;p&gt;A virtual machine gives you a separate operating system. It does not automatically give that operating system a dedicated gaming PC. The hypervisor decides how the guest sees the hardware, and the graphics path is often the deciding factor between “the game opens” and “the game is playable.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/assembly_managing-gpu-devices-in-virtual-machines_configuring-and-managing-virtualization" rel="noopener noreferrer"&gt;Red Hat: Managing GPU devices in virtual machines&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://instinct.docs.amd.com/projects/amdgpu-docs/en/docs-31.50.0/virtualization/index.html" rel="noopener noreferrer"&gt;AMD GPU virtualization documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.nvidia.com/vgpu/20.0/grid-vgpu-user-guide/index.html" rel="noopener noreferrer"&gt;NVIDIA Virtual GPU Software User Guide&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>virtualmachine</category>
      <category>gaming</category>
      <category>vmware</category>
    </item>
    <item>
      <title>Why Some Games Still Do Not Work on Linux</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:57:25 +0000</pubDate>
      <link>https://dev.to/rrouwelng/why-some-games-still-do-not-work-on-linux-2g8j</link>
      <guid>https://dev.to/rrouwelng/why-some-games-still-do-not-work-on-linux-2g8j</guid>
      <description>&lt;p&gt;Linux gaming has changed dramatically because of Steam Play and Proton. Many Windows games can now run with a click, without a Windows installation. But “many games work” is not the same as “every game works.” When a title fails, the cause may have little to do with Linux in general. It can be a particular launcher, a media component, anti-cheat configuration, DRM, or a recent game update.&lt;/p&gt;

&lt;p&gt;The most useful way to think about compatibility is as a chain. The game must start, its Windows APIs must behave as expected, its graphics calls must translate correctly, the Linux driver must support the required features, and online services must accept the environment. A failure in any one link can stop the game.&lt;/p&gt;

&lt;h2&gt;
  
  
  Windows API differences
&lt;/h2&gt;

&lt;p&gt;Proton is based on Wine, which implements Windows APIs on Linux. It is not a copy of Windows. Most common application and game interfaces have substantial support, but an application may depend on a behavior that is missing, incomplete, or different from what the game expects.&lt;/p&gt;

&lt;p&gt;Games also ship with support software. A launcher may use a web framework or a Windows-specific component. A patcher may assume a particular file layout. A login flow can depend on embedded browser behavior. The game itself may be compatible while its launcher is not, or vice versa.&lt;/p&gt;

&lt;p&gt;Valve has identified technologies such as some .NET/WPF launchers and Media Foundation video as areas that can delay Proton compatibility. This does not mean every game using those technologies fails; it means such dependencies are common sources of extra work. &lt;a href="https://partner.steamgames.com/doc/steamhardware/proton" rel="noopener noreferrer"&gt;Valve’s Proton documentation&lt;/a&gt; discusses several developer-facing compatibility issues.&lt;/p&gt;

&lt;h2&gt;
  
  
  Graphics translation is not magic
&lt;/h2&gt;

&lt;p&gt;A Windows game may use Direct3D, while Linux commonly provides Vulkan and OpenGL through the graphics driver. Proton includes translation components that map supported Direct3D behavior to Vulkan. This translation is complex. Games exercise different features, and a bug can appear only with a certain GPU generation, driver version, rendering setting, or scene.&lt;/p&gt;

&lt;p&gt;A game might launch but show missing textures, broken shadows, shader stutter, or a crash when a particular effect appears. These symptoms do not all point to the same cause. A driver update could fix a Vulkan bug; a Proton update could fix a translation issue; or a game update could introduce a new behavior that the compatibility layer has not yet handled.&lt;/p&gt;

&lt;p&gt;Native Linux drivers also differ by vendor and hardware generation. A feature available on one GPU may not be supported on another. The fact that a game uses Vulkan does not mean it is automatically compatible with every Vulkan driver.&lt;/p&gt;

&lt;h2&gt;
  
  
  Anti-cheat and competitive multiplayer
&lt;/h2&gt;

&lt;p&gt;Anti-cheat is one of the most visible reasons a game may not work. Some anti-cheat vendors support Proton-compatible operation, but the game developer must often enable or configure it for each title. Valve’s documentation notes that Easy Anti-Cheat and BattlEye can be supported with title-specific setup. A game's use of either product is not enough by itself to guarantee Linux support.&lt;/p&gt;

&lt;p&gt;Kernel-level anti-cheat systems present a different problem. Their Windows components expect to operate in the Windows kernel. Wine does not load a Windows kernel; it implements Windows APIs in user space on a Linux kernel. As a result, a Windows kernel driver cannot simply be installed and run as if Linux were Windows.&lt;/p&gt;

&lt;p&gt;Examples of games that have had Linux/Proton compatibility blocked or affected by anti-cheat include titles such as &lt;em&gt;Destiny 2&lt;/em&gt; and &lt;em&gt;Valorant&lt;/em&gt;. Their compatibility status and publisher policies can change, so do not treat a years-old list as a current promise. Before buying or troubleshooting a competitive game, check recent reports and the publisher’s current support statement. Some publishers explicitly block or do not support play through Proton.&lt;/p&gt;

&lt;p&gt;This limitation is not something users should try to bypass. Anti-cheat systems protect multiplayer environments, and evading them can violate the game’s rules or risk an account. The durable solution is for the publisher and anti-cheat vendor to support the platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  DRM, launchers, and updates
&lt;/h2&gt;

&lt;p&gt;Digital rights management and third-party launchers can add extra layers between Steam and the game. A launcher may update independently, require a web login, or install a background service. The game can stop working because the launcher changes, even if the game binary and Proton have not changed.&lt;/p&gt;

&lt;p&gt;DRM and anti-tamper systems can also interact poorly with Wine’s environment. Valve notes that anti-tamper and DRM can require time to become functional in Wine and may introduce delays. In practice, a title that launched successfully last month can break after a launcher or game patch.&lt;/p&gt;

&lt;p&gt;This is why it helps to record the date and version when reporting a failure. “This game does not work on Linux” is too broad if one update broke the game for a week and a later update fixed it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Video playback and codecs
&lt;/h2&gt;

&lt;p&gt;Some games use video during startup, cutscenes, or tutorials. If a Windows media framework or codec is unavailable or behaves differently, the game may show a black screen, skip a video, or fail during a transition. A video issue may be mistaken for a graphics crash because it occurs in the middle of gameplay.&lt;/p&gt;

&lt;p&gt;The correct fix depends on the title and Proton version. Installing random codec packages into the host system is rarely the first step. Check current game reports and the distribution-specific guidance before changing system libraries.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do when a game fails
&lt;/h2&gt;

&lt;p&gt;Start with the basics. Check that the game is in your Steam library and whether other users have reported current success. Verify the installed game files in Steam. Use the default Proton version first, then try a different official version if the reports suggest it. Restart after a game update and note whether the behavior changes.&lt;/p&gt;

&lt;p&gt;If you use launch options, test one change at a time. Removing multiple variables is often more effective than copying a long command from an old discussion. If the game fails at login, that points toward a different area than a crash after a shader-heavy scene.&lt;/p&gt;

&lt;p&gt;When a game is blocked by publisher policy or incompatible anti-cheat, switching Proton versions is unlikely to be a lasting fix. That is an upstream support issue, not a missing package on your desktop.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compatibility is a moving target
&lt;/h2&gt;

&lt;p&gt;Linux compatibility is not a single yes-or-no property. A title can work in single-player but fail in multiplayer. It can work on one GPU and not another. It can be playable today and broken by tomorrow’s patch. It can launch but have poor controller support, broken video, or degraded performance.&lt;/p&gt;

&lt;p&gt;That variability is frustrating, but it is also why community reports are valuable. Check their dates, hardware, Proton versions, and descriptions. A recent report on a similar setup is more useful than a one-word rating from several years ago.&lt;/p&gt;

&lt;p&gt;The key lesson is to diagnose the layer that failed. Proton handles compatibility; graphics translation handles rendering APIs; drivers handle the GPU; launchers and DRM add vendor-controlled components; and anti-cheat depends on decisions by developers and providers. Once those parts are separated, “Linux can’t run this game” becomes a much more precise question: which component is preventing it, and who can change it?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://partner.steamgames.com/doc/steamhardware/proton" rel="noopener noreferrer"&gt;Valve Steamworks: Steam Hardware and Proton&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ValveSoftware/Proton" rel="noopener noreferrer"&gt;ValveSoftware/Proton on GitHub&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.protondb.com/" rel="noopener noreferrer"&gt;ProtonDB&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>proton</category>
    </item>
    <item>
      <title>ProtonDB: How to Check Whether a Steam Game Works on Linux</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:57:12 +0000</pubDate>
      <link>https://dev.to/rrouwelng/protondb-how-to-check-whether-a-steam-game-works-on-linux-5333</link>
      <guid>https://dev.to/rrouwelng/protondb-how-to-check-whether-a-steam-game-works-on-linux-5333</guid>
      <description>&lt;p&gt;Before buying a Windows-only game for a Linux PC or Steam Deck, it is smart to ask someone who has already tried it. ProtonDB collects community reports about running games with Proton. It is not an official Valve compatibility guarantee, but it can be one of the most useful tools for figuring out what to expect.&lt;/p&gt;

&lt;p&gt;The important part is knowing how to read the reports. A rating without context can hide differences in hardware, game version, settings, and date. This guide shows how to use ProtonDB as a practical research tool rather than a simple traffic-light chart.&lt;/p&gt;

&lt;h2&gt;
  
  
  What ProtonDB is—and what it is not
&lt;/h2&gt;

&lt;p&gt;ProtonDB is a community project that gathers reports from players testing Steam games with Proton on Linux and Steam Deck. It aggregates reports and displays recommendations and user experiences. &lt;a href="https://www.protondb.com/" rel="noopener noreferrer"&gt;The ProtonDB site&lt;/a&gt; explains its goal and provides game pages, reports, and contribution tools.&lt;/p&gt;

&lt;p&gt;It is not Valve’s official Steam Deck verification system. Steam’s Verified and Playable labels are part of Valve’s Deck compatibility program and evaluate more than whether a game launches through Proton. ProtonDB focuses on users’ reported experiences. The two systems answer related but different questions.&lt;/p&gt;

&lt;p&gt;ProtonDB is also not a promise that a game will work on every Linux computer. A report from a Steam Deck is not a perfect match for a desktop with a different GPU. A report from one Proton release may not apply after a major game update.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding a game
&lt;/h2&gt;

&lt;p&gt;Go to ProtonDB and search for the game title. You can also open a game page directly from its Steam app ID, which is the number in the Steam store URL. The game page normally shows a community tier or summary, recent reports, and information contributed by users.&lt;/p&gt;

&lt;p&gt;Start by looking at the recent reports, not just the headline rating. Look for the operating context, including whether the person tested on desktop Linux or Steam Deck, the Proton version, GPU, distribution, and any special configuration. Reports that provide these details are more useful because you can compare them to your own setup.&lt;/p&gt;

&lt;p&gt;Pay attention to the date. A report from before a launcher overhaul or a major game patch might describe a version that no longer exists. Likewise, an old negative report might have been fixed by a newer Proton release. Compatibility changes over time in both directions.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do the ratings tell you?
&lt;/h2&gt;

&lt;p&gt;ProtonDB uses community report data to summarize how well games run. The exact meaning of a tier is less important than the evidence behind it. A strong aggregate score can mean many people report success, but it does not necessarily mean the game is flawless or that all features work.&lt;/p&gt;

&lt;p&gt;Read the report text. Does the game reach the main menu? Is the whole campaign playable? Does multiplayer work? Are there visual glitches? Does the author need a launch option? Is performance acceptable on hardware like yours?&lt;/p&gt;

&lt;p&gt;A rating can combine experiences that are not equivalent. Someone may call a game “playable” because it launches and runs at a tolerable frame rate, while another person may consider a broken cutscene a dealbreaker. The details tell you what the rating means for your priorities.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate desktop and Steam Deck experiences
&lt;/h2&gt;

&lt;p&gt;The Steam Deck has a defined hardware and software environment, including a particular controller layout and display. A game can be comfortable on Deck but inconvenient on a desktop, or the other way around. Desktop Linux systems vary widely in GPU, drivers, monitors, desktop environments, and input devices.&lt;/p&gt;

&lt;p&gt;When checking a report, make sure you are comparing like with like. A Deck report can be helpful for Proton compatibility, but it cannot tell you exactly how the game will perform on your desktop GPU. A desktop report with the same GPU family and similar driver stack may be more predictive for graphics performance.&lt;/p&gt;

&lt;p&gt;If you own a Deck, look for Deck-specific reports and also check Valve’s official compatibility label. If you use a Linux desktop, prioritize reports with similar hardware and Proton versions.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to use a report before purchase
&lt;/h2&gt;

&lt;p&gt;First, search for the exact edition of the game you plan to buy. Some titles have separate app entries for demo versions, test branches, remasters, or launchers. Then inspect several recent reports. A single report could be affected by a temporary outage or unusual local configuration.&lt;/p&gt;

&lt;p&gt;Next, check for multiplayer dependencies. If the game uses anti-cheat, a report that says “launches” may not mean online play works. Read the report for the game mode tested and look for current information from the publisher. ProtonDB can document user experience, but the game developer controls server access and anti-cheat configuration.&lt;/p&gt;

&lt;p&gt;Finally, consider the cost of failure. If you are buying a single-player game with a refund window, you may be comfortable trying it. If you need a competitive game for a team event, an uncertain community report may not be enough. Check the store’s current refund terms directly rather than relying on assumptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use fixes carefully
&lt;/h2&gt;

&lt;p&gt;Reports sometimes include launch options or workarounds. Treat them as clues, not guaranteed commands. Before pasting one into Steam, understand what it changes. Some options select a compatibility component; others alter graphics behavior or environment variables. A fix for a particular Proton release may be unnecessary or harmful on another version.&lt;/p&gt;

&lt;p&gt;Try the simplest setup first: install the game, use Steam’s default compatibility choice, and test. Then follow a recent report that matches your environment. Change one setting at a time and record the result. This makes it much easier to undo a workaround that does not help.&lt;/p&gt;

&lt;p&gt;Avoid downloading replacement executables or untrusted DLLs from random file hosts. That can create security risks, violate the game’s rules, or make troubleshooting harder. Prefer Steam’s built-in tools, official Proton releases, and advice from credible project communities.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to write a useful report
&lt;/h2&gt;

&lt;p&gt;If you test a game, add a report that helps the next person. Include the operating system and version, GPU, driver, Proton version, and whether you tested on desktop or Deck. Describe the behavior plainly: Did it launch? Did the tutorial work? Were you able to join an online match? Did the game crash after a particular step?&lt;/p&gt;

&lt;p&gt;If you used a workaround, say exactly what it was and whether it was required. If you tested after a game patch, mention when. Avoid claiming universal compatibility based on one machine. “Runs well on my Radeon RX 7600 with Proton X in single-player at 1080p” is much more informative than “Works perfectly.”&lt;/p&gt;

&lt;h2&gt;
  
  
  Interpreting uncertainty
&lt;/h2&gt;

&lt;p&gt;A page with few reports does not prove the game is broken. It means there is limited evidence. A page with many positive reports does not eliminate the possibility of a problem on your hardware. ProtonDB is strongest when it offers recent, detailed reports from people with similar setups.&lt;/p&gt;

&lt;p&gt;Use it alongside official sources: the Steam store page, Valve’s Deck compatibility label, publisher announcements, and current discussions. If the problem is a recent patch, look for reports posted after that patch. If anti-cheat is involved, prioritize official developer statements because compatibility can depend on server-side decisions.&lt;/p&gt;

&lt;p&gt;ProtonDB works best as a living notebook maintained by players. Search the game, compare recent reports, check the details behind the tier, and contribute what you learn. A few minutes of careful reading can save hours of guesswork—and a good report can help the next Linux player decide with confidence.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.protondb.com/" rel="noopener noreferrer"&gt;ProtonDB&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.protondb.com/news/steam-deck-reports-are-here" rel="noopener noreferrer"&gt;ProtonDB: Steam Deck reports are here&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://partner.steamgames.com/doc/steamhardware/compat" rel="noopener noreferrer"&gt;Valve Steamworks: Deck compatibility documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>steam</category>
      <category>proton</category>
    </item>
    <item>
      <title>AMD’s Open-Source Linux Graphics Drivers: What the Stack Looks Like</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Mon, 16 Nov 2026 21:55:59 +0000</pubDate>
      <link>https://dev.to/rrouwelng/amds-open-source-linux-graphics-drivers-what-the-stack-looks-like-45bn</link>
      <guid>https://dev.to/rrouwelng/amds-open-source-linux-graphics-drivers-what-the-stack-looks-like-45bn</guid>
      <description>&lt;p&gt;One common misconception about Linux graphics is that there is one “AMD driver.” In practice, graphics support is a stack. It includes a kernel driver, user-space drivers for graphics APIs, libraries, and supporting components. Understanding the pieces makes it easier to troubleshoot games and explains why AMD’s open-source approach is important to Linux gaming.&lt;/p&gt;

&lt;p&gt;This article focuses on the general upstream Linux stack for modern AMD GPUs. Specific packages and driver choices vary by distribution and hardware generation, so consult your distribution’s documentation before changing anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Kernel driver and user-space driver
&lt;/h2&gt;

&lt;p&gt;Linux graphics divides work between the kernel and user space. The kernel-mode driver, commonly &lt;code&gt;amdgpu&lt;/code&gt; for modern Radeon hardware, handles tasks such as GPU scheduling, memory management, power management, display support, and communication with the device. Applications generally do not call this kernel driver directly through a graphics API.&lt;/p&gt;

&lt;p&gt;User-space drivers implement APIs such as Vulkan and OpenGL. On AMD systems, Mesa provides widely used open-source user-space graphics drivers. RADV is Mesa’s Vulkan driver for AMD GCN and RDNA GPUs. Mesa’s documentation states that RADV is included by many Linux distributions and is used on Steam Deck. &lt;a href="https://docs.mesa3d.org/drivers/radv.html" rel="noopener noreferrer"&gt;RADV’s documentation&lt;/a&gt; explains this architecture in detail.&lt;/p&gt;

&lt;p&gt;This split is not unique to AMD. Modern graphics systems commonly keep hardware management in the kernel and API implementation in user space. It lets graphics APIs evolve without putting every piece of application-facing functionality into the kernel.&lt;/p&gt;

&lt;h2&gt;
  
  
  What RADV does
&lt;/h2&gt;

&lt;p&gt;A Vulkan game calls Vulkan functions through the loader. The loader finds an available Vulkan implementation, such as RADV, which implements the API for the GPU. RADV translates application work into commands and shaders the hardware can execute, then communicates with the kernel driver to submit that work.&lt;/p&gt;

&lt;p&gt;Shader compilation is one of the major tasks. A Vulkan application can provide shaders in SPIR-V intermediate form. RADV and Mesa’s compiler stack transform and optimize them, then generate instructions for the specific GPU architecture. This is why shader compilation can affect loading times and stutter, particularly when the game has not yet built a cache for a particular workload.&lt;/p&gt;

&lt;p&gt;RADV is not a separate downloadable product that every user must install manually. On many distributions, it arrives as part of the Mesa packages and is selected automatically through the Vulkan loader. Package names and optional components differ by distribution.&lt;/p&gt;

&lt;h2&gt;
  
  
  AMDVLK, RADV, and choices
&lt;/h2&gt;

&lt;p&gt;AMD has published and supported more than one Vulkan driver path over time, including the open-source RADV driver in Mesa and AMD’s own Vulkan driver releases. Which options are available and recommended can vary by GPU, distribution, and release. Do not assume that “official” always means faster or that community-developed always means unsupported. Driver performance and correctness depend on the workload and the current versions.&lt;/p&gt;

&lt;p&gt;For many desktop Linux users, the distribution’s default Mesa stack is a sensible starting point. It receives updates through normal system channels and integrates with the kernel and Vulkan loader supplied by the distribution. Installing a second Vulkan driver without a clear reason can create confusion about which implementation an application is loading.&lt;/p&gt;

&lt;p&gt;To inspect Vulkan support, use your distribution’s recommended tools, such as &lt;code&gt;vulkaninfo&lt;/code&gt; if installed. That can show the Vulkan devices and implementations visible to the system. A game launched through Steam may also use a runtime environment, so the libraries it sees can differ from what a terminal command prints.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why open source matters
&lt;/h2&gt;

&lt;p&gt;An open-source driver can be inspected, modified, and improved by a broad community. Mesa development happens in the open, with contributions from hardware vendors and independent developers. Fixes can benefit many distributions and users rather than being tied to one vendor installer.&lt;/p&gt;

&lt;p&gt;Open source does not automatically mean perfect support or instant fixes. A new GPU generation may need kernel, firmware, Mesa, and distribution updates before all features are available. Some hardware features may require proprietary firmware blobs even when the driver code is open. The overall system can be a mix of open driver code and separately licensed firmware.&lt;/p&gt;

&lt;p&gt;The practical advantage is that much of the graphics stack is integrated into the regular Linux development ecosystem. Users often receive updates through their distribution rather than manually installing a separate driver package from a vendor website. That can simplify maintenance, but it also means a distribution’s release cadence matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  AMD graphics for Proton gaming
&lt;/h2&gt;

&lt;p&gt;When a Windows game runs through Proton, the graphics path may involve a Windows-facing Direct3D interface, a translation component such as DXVK or vkd3d-proton, Vulkan, and then RADV plus the kernel driver. Each part can affect compatibility and performance.&lt;/p&gt;

&lt;p&gt;If a game crashes or renders incorrectly, the cause might be Proton, the graphics translation layer, Mesa, the kernel driver, the GPU firmware, or the game itself. A symptom such as shader stutter may be related to compilation and caching rather than a defective card. A missing Vulkan device can indicate a driver or 32-bit library issue, depending on the application and distribution.&lt;/p&gt;

&lt;p&gt;That layered model helps avoid random troubleshooting. Check whether Vulkan works outside the game. Confirm that the system is using the intended GPU. Then test the game with a default Proton version before changing driver settings or environment variables. If a problem appeared after an update, identify which component changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Updating safely
&lt;/h2&gt;

&lt;p&gt;For most users, update the kernel, Mesa, and firmware through the distribution’s supported package manager and release process. On Fedora, that typically means DNF for packages. On image-based systems such as Fedora Silverblue, package management differs, so use the system’s documented workflow rather than applying ordinary mutable-system commands.&lt;/p&gt;

&lt;p&gt;Avoid mixing repositories or replacing core graphics libraries casually. A newer Mesa build can fix a game-specific regression, but it can also introduce another issue or create mismatched dependencies. If you decide to use a newer graphics stack, use a trusted source intended for your distribution and keep a rollback plan.&lt;/p&gt;

&lt;p&gt;When asking for help, share the GPU model, kernel version, Mesa version, distribution, Vulkan implementation, and game/Proton version. “AMD graphics is broken” is not enough information to isolate a problem in a layered stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  A modern stack, not a single installer
&lt;/h2&gt;

&lt;p&gt;AMD’s Linux graphics support is best understood as a set of cooperating components. The kernel’s &lt;code&gt;amdgpu&lt;/code&gt; driver manages hardware and memory; Mesa’s RADV provides Vulkan in user space; other Mesa drivers provide OpenGL; and games or Proton interact with those APIs through additional layers.&lt;/p&gt;

&lt;p&gt;For many players, the best setup is simply the supported default from a current distribution. Knowing what sits beneath that default helps when something breaks—and it shows why open-source driver development is a major part of Linux gaming’s progress.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.mesa3d.org/drivers/radv.html" rel="noopener noreferrer"&gt;Mesa documentation: RADV&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.mesa3d.org/" rel="noopener noreferrer"&gt;Mesa project documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://partner.steamgames.com/doc/steamhardware/proton" rel="noopener noreferrer"&gt;Valve Steamworks: Steam Hardware and Proton&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>linux</category>
      <category>amd</category>
      <category>opensource</category>
      <category>gaming</category>
    </item>
    <item>
      <title>What happened to game optimization ?</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Wed, 04 Nov 2026 10:13:26 +0000</pubDate>
      <link>https://dev.to/rrouwelng/what-happened-to-game-optimization--dpo</link>
      <guid>https://dev.to/rrouwelng/what-happened-to-game-optimization--dpo</guid>
      <description>&lt;p&gt;Here is a draft you can copy, tweak, or expand directly in your editor:&lt;/p&gt;




&lt;h1&gt;
  
  
  What Happened to Game Optimization?
&lt;/h1&gt;

&lt;p&gt;If you’ve tried playing a high-profile PC release in recent years, you’ve likely encountered it: unexpected stuttering, severe frame drops, astronomical VRAM requirements, or a day-one patch measuring in tens of gigabytes.&lt;/p&gt;

&lt;p&gt;It begs the question: &lt;strong&gt;Why does it feel like modern games are launching poorly optimized, even on hardware that costs thousands of dollars?&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Upscaling Has Shifted from a Boost to a Crutch
&lt;/h2&gt;

&lt;p&gt;Technologies like NVIDIA DLSS, AMD FSR, and Intel XeSS were revolutionary when introduced—promising to extend the lifespan of older GPUs and push high frame rates at $4\text{K}$.&lt;/p&gt;

&lt;p&gt;However, a subtle shift has occurred in modern game development. Rather than treating AI upscaling as an extra performance boost, many titles now list upscaling as a &lt;strong&gt;baseline system requirement&lt;/strong&gt; just to achieve $60\text{ FPS}$ at $1080\text{p}$. When rendering natively is no longer the primary target during development, native performance inevitably suffers.&lt;/p&gt;




&lt;h2&gt;
  
  
  2. Low-Level APIs: More Control, Higher Stakes
&lt;/h2&gt;

&lt;p&gt;In the era of DirectX 11, the graphics driver did a lot of heavy lifting under the hood, managing memory and optimizing shader compilation automatically.&lt;/p&gt;

&lt;p&gt;With low-level APIs like &lt;strong&gt;DirectX 12&lt;/strong&gt; and &lt;strong&gt;Vulkan&lt;/strong&gt;, control was handed directly to game developers. This drastically raised the performance ceiling, but it also placed an enormous burden on dev teams. If an engine doesn't explicitly handle Pipeline State Objects (PSOs) or pre-compile shaders properly, players experience severe, jarring shader compilation stutter—a hallmark issue of this generation.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. Asset Explosion &amp;amp; VRAM Bottlenecks
&lt;/h2&gt;

&lt;p&gt;Games today are massive. Uncompressed $4\text{K}$ textures, complex geometry, and advanced illumination systems mean games regularly cross $100\text{–}150\text{ GB}$.&lt;/p&gt;

&lt;p&gt;This asset explosion directly impacts memory bandwidth:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;VRAM Overhead:&lt;/strong&gt; Mid-range GPUs equipped with $8\text{ GB}$ of VRAM quickly run out of memory overhead when handling modern texture pools.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ray Tracing &amp;amp; Global Illumination:&lt;/strong&gt; Real-time lighting technologies like path tracing provide incredible realism, but they require immense raw computational budget compared to traditional baked lighting.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  4. Production Deadlines &amp;amp; "Fix It Later" Culture
&lt;/h2&gt;

&lt;p&gt;Optimization is traditionally one of the final phases of game production. When hard release dates are set for fiscal quarters or holiday windows, optimization time is often squeezed to make room for bug fixing and core gameplay completion.&lt;/p&gt;

&lt;p&gt;Compounding this is the prevalence of post-launch updates. The normalization of day-one patches and live-service roadmaps has created an environment where shipping a game in a rough state—and optimizing it over the following six months—is increasingly treated as an acceptable tradeoff.&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Game optimization hasn't disappeared, but the complexity of modern hardware combinations, low-level APIs, and ambitious graphics pipelines has made it harder than ever to achieve.&lt;/p&gt;

&lt;p&gt;As developers, finding the balance between leveraging automated engine features and dedicating time to low-level profiling will be crucial to restoring player trust on launch day.&lt;/p&gt;

</description>
      <category>gamedev</category>
    </item>
    <item>
      <title>Why linux distros are called distros</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Tue, 06 Oct 2026 07:36:52 +0000</pubDate>
      <link>https://dev.to/rrouwelng/why-linux-distros-are-called-distros-3bhn</link>
      <guid>https://dev.to/rrouwelng/why-linux-distros-are-called-distros-3bhn</guid>
      <description>&lt;h1&gt;
  
  
  Why Linux Distros Are Called "Distros"
&lt;/h1&gt;

&lt;p&gt;If you were once fed up with Windows and decided to venture into Linux, you may have heard the word "distro" tossed around in YouTube explanation videos debating which Linux distribution is best for you.&lt;/p&gt;

&lt;p&gt;At first, you might consider Linux to be a complete, all-in-one operating system just like Windows 10 or 11. But that isn't really the case. To debug this belief, we first have to understand what actually makes up an operating system.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Makes Up an Operating System?
&lt;/h2&gt;

&lt;p&gt;While an operating system contains many components, we can break it down into four main pillars:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Kernel:&lt;/strong&gt; The heart of the OS. It manages hardware resources and coordinates background operations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User Interface (UI):&lt;/strong&gt; The visual layer you interact with—the desktop, windows, icons, and menus.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Device Drivers:&lt;/strong&gt; Specialized software used by the kernel to communicate with hardware components like your GPU, Wi-Fi card, or keyboard.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shell:&lt;/strong&gt; The direct text-based interface (command line) used to interact directly with the kernel.&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Linux Is Just a Kernel
&lt;/h2&gt;

&lt;p&gt;A &lt;strong&gt;kernel&lt;/strong&gt; is the foundational core of an operating system—the bridge that connects your hardware to your software. It manages CPU schedules, RAM allocation, and device drivers so programs can run without crashing your system.&lt;/p&gt;

&lt;p&gt;Because of that definition, your daily experience running &lt;strong&gt;Linux Mint&lt;/strong&gt; or &lt;strong&gt;Fedora with KDE&lt;/strong&gt; feels vastly different from a bare-bones kernel. &lt;/p&gt;

&lt;p&gt;On its own, a kernel is like a car engine: essential for movement, but completely unusable until you add a chassis, wheels, seats, a steering wheel, and a dashboard. &lt;br&gt;
A standalone kernel will boot your hardware, but is essentially unusable without the other parts of an operating system.&lt;/p&gt;




&lt;h2&gt;
  
  
  How "Distros" Come to Life
&lt;/h2&gt;

&lt;p&gt;Because the Linux kernel is open-source, different groups of people—companies, non-profit organizations, and independent developer communities—take the core kernel and build complete operating systems around it. &lt;/p&gt;

&lt;p&gt;They combine:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The Linux Kernel&lt;/strong&gt; (the underlying engine)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GNU Utilities &amp;amp; Shell&lt;/strong&gt; (the command-line tools)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Desktop Environments&lt;/strong&gt; (like GNOME, KDE Plasma, or XFCE)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Package Managers&lt;/strong&gt; (tools like &lt;code&gt;apt&lt;/code&gt; or &lt;code&gt;dnf&lt;/code&gt; to install software)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pre-installed Applications&lt;/strong&gt; (browsers, media players, and text editors)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because these groups bundle, configure, and &lt;strong&gt;distribute&lt;/strong&gt; these complete software packages to the public, the final products are called &lt;strong&gt;distributions&lt;/strong&gt;—or &lt;strong&gt;"distros"&lt;/strong&gt; for short.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Power of Choice
&lt;/h2&gt;

&lt;p&gt;This distinction between the kernel and a distribution is what makes the Linux ecosystem unique. Personally, I like fedora. I am not able to tell you why, I just do.&lt;/p&gt;

&lt;p&gt;Because Linux isn't controlled by a single company, no single entity dictates how your computer should look or behave:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Linux Mint&lt;/strong&gt; bundles the kernel with user-friendly desktops to give former Windows users a smooth, familiar transition.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fedora&lt;/strong&gt; pairs the kernel with cutting-edge tools and GNOME for developers who want the latest technologies. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Arch Linux&lt;/strong&gt; leaves the bundle choice entirely to you, letting you build a tailored system from scratch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But you do not have to buy into the stereotypes. The beauty of linux is the customizability. My fedora installation felt more like an arch linux install because I wanted it to. Just a blank black screen with glowing green text. &lt;/p&gt;

&lt;p&gt;My first linux installation was nobara linux, a game focused operating system maintained by glorious eggroll or eggy for short.(Look him up he's cool). But the issues i encountered made me switch back to windows 11. (More about this sistuation in a later post)&lt;/p&gt;

&lt;p&gt;Ultimately, when you install "Linux," you aren't just installing an operating system-you are choosing a custom distribution crafted by a community that shares your vision for computing.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>fedoralinux</category>
    </item>
    <item>
      <title>How the python package installer works</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Sun, 26 Jul 2026 09:11:16 +0000</pubDate>
      <link>https://dev.to/rrouwelng/how-the-python-package-installer-works-3k13</link>
      <guid>https://dev.to/rrouwelng/how-the-python-package-installer-works-3k13</guid>
      <description>&lt;p&gt;My first encounter with &lt;strong&gt;pip&lt;/strong&gt; was trying to run a Python script that imported the &lt;code&gt;requests&lt;/code&gt; library, only to be met with an import error. The fix turned out to be straightforward: using &lt;strong&gt;pip&lt;/strong&gt;, Python's package installer.&lt;/p&gt;

&lt;p&gt;To use pip, you need to have Python installed on your system. The basic command to install any library is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install&lt;/span&gt; &amp;lt;package-name&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Best Practice: Using a Virtual Environment (&lt;code&gt;venv&lt;/code&gt;)
&lt;/h2&gt;

&lt;p&gt;Before installing packages everywhere, it’s best to create an isolated workspace for your project called a &lt;strong&gt;virtual environment&lt;/strong&gt;. This keeps package dependencies for different projects separate so they don't clash with each other or your system's main Python installation.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Create the environment
&lt;/h3&gt;

&lt;p&gt;Open your terminal in your project directory and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python &lt;span class="nt"&gt;-m&lt;/span&gt; venv venv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(This creates a folder named &lt;code&gt;venv&lt;/code&gt; containing a standalone copy of Python and pip.)&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Activate the environment
&lt;/h3&gt;

&lt;p&gt;Before installing anything, activate it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Windows:&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  venv\Scripts\activate
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;macOS / Linux:&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;  &lt;span class="nb"&gt;source &lt;/span&gt;venv/bin/activate
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once activated, your terminal prompt will show &lt;code&gt;(venv)&lt;/code&gt; at the beginning. Any &lt;code&gt;pip install&lt;/code&gt; commands you run now will stay inside this isolated environment.&lt;/p&gt;




&lt;h2&gt;
  
  
  Bulk Installing Dependencies with &lt;code&gt;requirements.txt&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;When you're running a Python script with multiple required packages, installing them one by one gets tedious. You can streamline this process by bulk installing everything at once using a requirements file.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1: Create a &lt;code&gt;requirements.txt&lt;/code&gt; file
&lt;/h3&gt;

&lt;p&gt;Create a standard text file named &lt;code&gt;requirements.txt&lt;/code&gt; in your project folder and list all your dependencies, one per line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;requests
pandas
numpy
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Step 2: Run the bulk install command
&lt;/h3&gt;

&lt;p&gt;With your virtual environment active, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; requirements.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Specifying Package Versions
&lt;/h2&gt;

&lt;p&gt;Sometimes, the newest version of a library breaks compatibility with other packages in your project. To prevent this, you can specify exact version numbers directly inside your &lt;code&gt;requirements.txt&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;requests==2.31.0
pandas&amp;gt;=2.0.0
numpy&amp;lt;=1.24.0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;==&lt;/code&gt;&lt;/strong&gt; installs an exact version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;&amp;gt;=&lt;/code&gt;&lt;/strong&gt; or &lt;strong&gt;&lt;code&gt;&amp;lt;=&lt;/code&gt;&lt;/strong&gt; sets a minimum or maximum allowed version.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>beginners</category>
      <category>python</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>From Arcade Cabinets to AI: How the GPU Changed Computing Forever</title>
      <dc:creator>Rouwel Ngacha</dc:creator>
      <pubDate>Thu, 23 Jul 2026 19:55:48 +0000</pubDate>
      <link>https://dev.to/rrouwelng/from-arcade-cabinets-to-ai-how-the-gpu-changed-computing-forever-a7m</link>
      <guid>https://dev.to/rrouwelng/from-arcade-cabinets-to-ai-how-the-gpu-changed-computing-forever-a7m</guid>
      <description>&lt;p&gt;Before graphics processing units (GPUs) became the powerhouse chips driving modern video games, scientific simulations, and artificial intelligence, computer graphics were slow, blocky, and severely limited. Understanding how we got from simple glowing dots to today's hyper-realistic 3D worlds requires looking back at a few key breakthroughs in computing history.&lt;/p&gt;




&lt;h2&gt;
  
  
  Part 1: In the Beginning — Legacy Systems &amp;amp; Early Graphics
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1950: The Whirlwind Computer
&lt;/h3&gt;

&lt;p&gt;The long story of computer graphics begins in 1950 with &lt;strong&gt;The Whirlwind&lt;/strong&gt;, a giant computer built for the U.S. Navy as a flight simulator. Powered by thousands of bulky vacuum tubes, Whirlwind could perform around 50,000 basic calculations per second.&lt;/p&gt;

&lt;p&gt;It commanded a cathode-ray tube (CRT) monitor to draw basic dots, shapes, and screen coordinates. While impressive for its time, Whirlwind wasn't actually an ancestor of the modern GPU—it was simply an early milestone showing that computers could display visual information.&lt;/p&gt;

&lt;h3&gt;
  
  
  1970s–1980s: The Arcade Era
&lt;/h3&gt;

&lt;p&gt;The true lineage of the modern GPU started in arcade cabinets during the 1970s and 1980s.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Arcade Hardware:&lt;/strong&gt; Arcade machines (like those running &lt;em&gt;Pac-Man&lt;/em&gt;, &lt;em&gt;Donkey Kong&lt;/em&gt;, or &lt;em&gt;Galaga&lt;/em&gt;) used specialized graphics chips designed for "fixed functions". These chips were custom-built to quickly animate moving characters (sprites) and background tiles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Home PCs:&lt;/strong&gt; In contrast, early personal computers relied entirely on their Central Processing Unit (CPU) to draw graphics using software. Because CPUs had to process every single pixel alongside normal system operations, home computer graphics lagged far behind arcade performance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fixed-function design of arcade hardware—doing one visual job extremely fast—became the blueprint for dedicated graphics hardware.&lt;/p&gt;




&lt;h2&gt;
  
  
  Part 2: The 3D Revolution &amp;amp; Standardizing the Pipeline
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How Early GPUs Worked: The Fixed Function Pipeline
&lt;/h3&gt;

&lt;p&gt;In the late 1980s and 1990s, computer graphics shifted from 2D sprites to 3D virtual environments made up of triangles. This created a multi-step pipeline:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Game Engine:&lt;/strong&gt; Determines the positions of 3D objects made of connected triangles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CPU:&lt;/strong&gt; Calculates game physics, rules, and coordinate movements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GPU (or 3D Accelerator):&lt;/strong&gt; Turns those 3D triangle coordinates into colored pixels.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Display:&lt;/strong&gt; Sends the finished 2D image out to your monitor.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[ Game Engine ] ──► [ CPU: Physics &amp;amp; Logic ] ──► [ GPU: 3D to Pixels ] ──► [ Display ]

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  The Early Limitation: The API Wars
&lt;/h3&gt;

&lt;p&gt;In the mid-1990s, every graphics card manufacturer created its own custom instruction language, known as an &lt;strong&gt;Application Programming Interface (API)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;If a developer wanted their game to run on different graphics cards, they had to write separate versions for proprietary formats like &lt;strong&gt;3dfx Glide&lt;/strong&gt;, &lt;strong&gt;S3 Metal&lt;/strong&gt;, &lt;strong&gt;PowerVR&lt;/strong&gt;, or &lt;strong&gt;OpenGL&lt;/strong&gt;. This fragmenting made developing 3D games difficult and expensive.&lt;/p&gt;




&lt;h2&gt;
  
  
  Part 3: The 1990s — Coining the "GPU" and Finding a Standard
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Key Milestones of the 1990s
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;1993 (3dfx Voodoo &amp;amp; Glide API):&lt;/strong&gt; 3dfx introduced the Voodoo card, delivering unprecedented 3D graphics performance for games like &lt;em&gt;Quake&lt;/em&gt;. Its proprietary Glide API dominated the market, but only worked on 3dfx hardware.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;1994 (Sony PlayStation):&lt;/strong&gt; Sony began using the term "GPU" to describe the custom 32-bit graphics processor inside the original PlayStation console.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;1998 (DirectX 7 &amp;amp; T&amp;amp;L):&lt;/strong&gt; Microsoft released &lt;strong&gt;DirectX 7&lt;/strong&gt;, featuring &lt;strong&gt;Transform &amp;amp; Lighting (T&amp;amp;L)&lt;/strong&gt; technology. DirectX established a universal software standard across all graphics cards, effectively ending the API wars and rendering proprietary formats like Glide obsolete.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;1999 (NVIDIA GeForce 256):&lt;/strong&gt; NVIDIA popularized the term "GPU" for PC hardware by launching the GeForce 256. It was marketed as the world’s first true GPU because it took over visual geometry calculations entirely from the CPU.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Key Takeaways
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Arcade roots:&lt;/strong&gt; Specialized graphics chips began in arcades to offload visual work from general-purpose CPUs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The 3D transition:&lt;/strong&gt; As games moved to 3D, dedicated cards were required to handle complex math involving thousands of triangles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Standardized software:&lt;/strong&gt; Microsoft DirectX unified how games talk to graphics hardware, setting the stage for modern PC gaming and computing.&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>ai</category>
      <category>computerscience</category>
      <category>hardware</category>
      <category>science</category>
    </item>
  </channel>
</rss>
