Fedora Workstation vs Windows

Agent access

1. ai-native userUse an official CLI

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence of any official AI-native CLI tool for Fedora Workstation; evidence only covers general OS features and unrelated community sentiment. This axis applies since a distro could plausibly ship an AI CLI tool, but no such capability is documented.

   ⚑ flag

   Windows~partialprobed5/10

   PowerShell is referenced as an official CLI/scripting tool for Windows, but the evidence pack gives no detail on AI-native features (e.g., agentic integration, official AI CLI like GitHub Copilot CLI) beyond a bare documentation link. missing for 10: evidence of AI-native CLI capabilities, hands-on validation, and details on how PowerShell integrates with agentic/AI workflows.

   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/powershell/scripting/overview”

   proof ↗⚑ flag

Agentic features

1. ai-native userOperate the product with natural-language commands

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence of natural-language command capability, AI assistant, or agentic control interface; only mentions of GNOME's keyword search (Super key) which is not natural-language interaction. Missing for 10: any AI/NLP command interface, voice/text natural-language control, agentic automation features.

   ⚑ flag

   Windows~partialclaimed3/10

   Windows ships Copilot integration in Office apps and Windows AI Foundry/Copilot+ PC APIs, suggesting some natural-language assistant capability, but there's no evidence of broad OS-level control via natural-language commands (e.g., managing files, settings, or apps purely through NL input). missing for 10: evidence of natural-language command support across core OS functions (file management, settings, system control), independent hands-on verification of Copilot's OS-level command capabilities.

   • [claimed-docs] “Get work done faster with Copilot inside your favorite Microsoft apps like Word, Excel, and PowerPoint.”
   • [claimed-docs] “Get started with Windows AI Foundry toolkit”
   • [claimed-docs] “Windows AI APIs for Copilot+ PCs”

   proof ↗⚑ flag

Api quality

1. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Fedora Workstation
   Fedora Workstation~partialclaimed4/10

   Fedora Workstation ships Boxes for one-click VM creation and built-in container tooling, which could be used as isolated sandbox environments separate from a production system, but there is no evidence of any AI-native testing workflow, staging/production data separation, or agent-specific sandbox tooling. missing for 10: explicit AI-native sandbox testing workflow, evidence of production-data isolation guarantees, and any hands-on corroboration of this use case.

   • [claimed-docs] “Boxes takes the guesswork out of using virtual machines. Just select the OS you want to install, and the app will do the rest.”
   • [claimed-docs] “Use the latest container tools from the Red Hat ecosystem. No setup required. Access the Red Hat container registry.”
   • [claimed-docs] “High-efficiency tools for creating, running and managing containers”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence of any sandbox/test environment feature for AI-native testing separate from production data; evidence covers UI frameworks, Store submission, telemetry complaints, and unrelated incidents.

   ⚑ flag

App installation

1. power-userChoose among official variants of the OS with different desktop environments and default apps

   weight 1 · round to Fedora Workstation
   Fedora Workstation~partialcommunity5/10

   Community evidence (e.g., fedora-comm-5, fedora-comm-16) confirms official KDE Spin variants exist and are used by power-users alongside the GNOME-based Workstation, supporting the story that alternate desktop environments are offered. However, the official docs pack only describes the GNOME Workstation edition and never mentions Spins, other DE options, or how default apps differ across variants. Missing for 10: first-party documentation of the Spins program, list of officially supported desktop environments, and default app differences per variant.

   • [community] “Fedora 39 KDE Spin has been flawless so far, and I love the window tiling native support. Also, suspend on Nvidia works again for me.”
   • [community] “Having used both on a regular basis, I hope they stick with GNOME. KDE is highly-configurable, which brings about a level of fun, but otherw…”
   • [community] “People may not like it, it may not be space efficient as some GNOME themes or macOS, but that thing works, doesn't crash, and improves produ…”

   proof ↗⚑ flag

   Windows—none0/10

   Windows does not offer official variants with different desktop environments/default apps akin to Linux distros; evidence pack only discusses editions (Pro/Home/Enterprise) which differ in licensing/features, not desktop environment choice, and there's no mention of alternate official DE options or default-app-swappable variants.

   ⚑ flag

2. power-userInstall thousands of applications directly from an official software catalog

   weight 3 · round to Windows
   Fedora Workstation!disputedcontradicted5/10

   Fedora's own docs claim one-click installs from Fedora repos, Flathub, or elsewhere (fedora-docs-8, fedora-docs-12), which aligns with GNOME Software's access to thousands of apps, but a hands-on community report describes a concrete failure of this exact promise—needing many manual commands to install common apps like Discord/Spotify, apps not running correctly, and GUI apps not appearing in the menu (fedora-comm-15). This is a specific counter-example to the 'easy install' claim, not just general skepticism. missing for 10: independent verification of catalog breadth/thousands of apps, corroboration that GNOME Software one-click install works smoothly across common apps, resolution of the comm-15 failure report.

   • [claimed-docs] “Easily install the very best desktop apps with the click of a button from Fedora's repositories, Flathub or anywhere else.”
   • [claimed-docs] “Easily install, update and manage software packages”
   • [community] “I chose popos, because the second I wanted discord or Spotify on fedora I had to go through a whole page of commands to do it, and it didn't…”

   proof ↗⚑ flag

   Windows~partialclaimed5/10

   Windows has the Microsoft Store as an official app catalog and docs confirm app submission and broad software/accessory compatibility, but the evidence pack never establishes scale ('thousands of apps') or a rich curated catalog experience, and no independent corroboration of catalog breadth is present. missing for 10: evidence of Store catalog size/breadth, independent corroboration of app-ecosystem richness, comparison to third-party app availability outside the Store.

   • [claimed-docs] “Submit your app to the Microsoft Store”
   • [claimed-docs] “Start with the fundamentals, design great experiences, build your app, and prepare it for distribution.”
   • [claimed-docs] “Yes, most applications, devices, and accessories that worked with Windows 10 are compatible with Windows 11.”

   proof ↗⚑ flag

3. switcherSearch and filter the app catalog by category to find familiar software

   weight 1 · round to Fedora Workstation
   Fedora Workstation~partialclaimed3/10

   Fedora's docs confirm a graphical app store (GNOME Software) that lets users install apps 'with the click of a button' from Fedora repos, Flathub, or elsewhere, implying a browsable catalog, but no evidence explicitly describes category-based browsing or filtering. Missing for 10: explicit documentation or screenshots of category filters/search UI, and any user/community confirmation of using categories to find familiar software.

   • [claimed-docs] “Easily install the very best desktop apps with the click of a button from Fedora's repositories, Flathub or anywhere else.”
   • [claimed-docs] “Easily install, update and manage software packages”

   proof ↗⚑ flag

   Windows—none0/10

   Evidence covers building/submitting apps to the Microsoft Store and general Windows features, but nothing describes app catalog browsing/search/filter-by-category functionality for end users to find familiar software.

   ⚑ flag

4. switcherInstall popular desktop apps with a single click from a built-in app store

   weight 3 · round to Windows
   Fedora Workstation!disputedcontradicted5/10

   Fedora ships GNOME Software, explicitly advertised as enabling one-click installs from Fedora repos, Flathub, or elsewhere (fedora-docs-8), which matches the story. However, a hands-on community report describes trying to install popular apps like Discord and Spotify and instead needing a full page of terminal commands, with installed GUI apps failing to appear in the app launcher (fedora-comm-15) — a concrete contradiction of the frictionless one-click claim for popular software. missing for 10: independent corroboration that one-click install reliably works for mainstream apps, and resolution of the conflicting hands-on failure report.

   • [claimed-docs] “Easily install the very best desktop apps with the click of a button from Fedora's repositories, Flathub or anywhere else.”
   • [community] “I chose popos, because the second I wanted discord or Spotify on fedora I had to go through a whole page of commands to do it, and it didn't…”

   proof ↗⚑ flag

   Windows~partialclaimed4/10

   Evidence confirms Windows has a Microsoft Store submission pipeline for apps, implying an app store exists for installing apps, but there's no evidence describing the consumer one-click install experience, curated popular-app catalog, or switcher-focused onboarding. missing for 10: evidence of the Store's consumer install UX, catalog breadth/popularity of apps, one-click install flow, and independent corroboration of ease-of-use for switchers.

   • [claimed-docs] “Submit your app to the Microsoft Store”
   • [claimed-docs] “Start with the fundamentals, design great experiences, build your app, and prepare it for distribution.”

   proof ↗⚑ flag

Bundled apps

1. switcherRely on built-in utilities like calendar, weather, maps, and clock apps out of the box

   weight 1 · round to Fedora Workstation
   Fedora Workstation~partialclaimed6/10

   First-party docs explicitly state Fedora Workstation includes Clocks, Weather and Maps utilities out of the box, and calendar integration is available via online accounts (though calendar app itself isn't separately confirmed). No independent/hands-on corroboration of these specific apps working well, and no mention of a bundled calendar app by name. Missing for 10: independent verification that Clocks/Weather/Maps work reliably out of the box, explicit confirmation of a bundled Calendar app, and any hands-on switcher testimonial about these specific utilities.

   • [claimed-docs] “Fedora Workstation includes a great set of utilities, like Clocks, Weather and Maps.”
   • [claimed-docs] “Optionally, bring your online calendar, contacts and data to the desktop with online accounts.”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence pack items mention built-in calendar, weather, maps, or clock apps shipping with Windows; the docs focus on app development frameworks (WinUI, MSIX) and unrelated features like Snap layouts, Windows Hello, and Copilot integration.

   ⚑ flag

Windows compatibility

1. power-userRun a full Windows environment in a virtual machine for apps not natively available

   weight 2 · round to Fedora Workstation
   Fedora Workstation~partialclaimed5/10

   Fedora ships GNOME Boxes for VM creation, which could host a Windows guest, but the evidence only describes generic 'select OS and install' functionality without confirming Windows-specific support, guest tools, or seamless integration for running Windows apps. Missing for 10: explicit mention of Windows guest support, performance/driver considerations, and independent hands-on confirmation of running Windows in Boxes.

   • [claimed-docs] “Boxes takes the guesswork out of using virtual machines. Just select the OS you want to install, and the app will do the rest.”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains nothing about Hyper-V, Windows Sandbox, or any native virtualization feature that would let a power-user run a full Windows VM. The only virtualization-adjacent mentions are about WSL (running Linux inside Windows), which is the opposite direction and does not address running Windows itself in a VM for legacy/native apps. Missing for 10: any documentation of Hyper-V/Windows Sandbox, VM licensing terms, or hands-on evidence of running Windows-in-VM for app compatibility.

   • [community] “I find it amazing that you can have such a functional Ubuntu environment by translating system calls... Microsoft calls it their 'Windows Su…”
   • [community] “Windows 10 is not bad at all, and I would have enjoyed keeping a Windows 10 machine handy with the new Ubuntu user land support.”

   proof ↗⚑ flag

Ai native tools

1. ai-native userDictate text anywhere in the system using built-in AI dictation

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence pack item mentions any AI dictation, voice-to-text, or speech input feature anywhere in Fedora Workstation; the docs cover VMs, containers, search, dark mode, and app installation but nothing about dictation or AI-native voice input.

   ⚑ flag

   Windows—none0/10

   The evidence pack mentions Live Captions, Copilot integration, and voice-related accessibility features like Studio Effects, but there is no mention of a system-wide AI dictation feature for typing/text input anywhere in Windows.

   ⚑ flag

Display comfort

1. power-userSwitch to dark mode or enable a night light to reduce eye strain

   weight 2 · round to Fedora Workstation
   Fedora Workstation✓fullclaimed8/10

   Official docs explicitly state users can flip a switch for dark mode and use night light to reduce glare/eye strain, directly matching the story. No independent hands-on corroboration of this specific feature is present, and no dispute evidence contradicts it. Missing for 10: independent/hands-on confirmation of dark mode/night light functioning as described.

   • [claimed-docs] “Flip a switch to turn on dark mode and give your eyes a break. Or use night light to reduce screen glare and help with sleep.”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence in the pack mentions dark mode, night light, or display/eye-strain settings; the docs cover app development, security, and unrelated features. Missing for 10: any documentation or community mention of dark mode toggle or night light/blue-light reduction feature.

   ⚑ flag

Productivity tools

1. power-userAutomate repetitive tasks using a built-in automation/scripting tool

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence in the pack mentions any built-in automation/scripting tool (e.g., macro recorder, shell scripting UI, GNOME automation features) for Fedora Workstation; the docs cover VM, containers, package management, and UI features only. missing for 10: any mention of a built-in automation/scripting tool, macro recorder, task scheduler, or scripting API for power-user automation.

   ⚑ flag

   Windows~partialprobed4/10

   Windows ships PowerShell as its built-in scripting/automation tool, confirmed only by a single official docs link in the evidence pack, with no detail on Task Scheduler, batch/VBScript, or independent corroboration of real-world automation workflows. Missing for 10: depth on Task Scheduler/other automation tools, hands-on user testimonials, and detail on PowerShell's actual automation capabilities beyond the link.

   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/powershell/scripting/overview”

   proof ↗⚑ flag

2. power-userAccess a unified clipboard history across text and images with one hotkey

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence pack items mention a clipboard manager, clipboard history, or hotkey-based clipboard access across text/images; GNOME's default clipboard has no built-in history feature and none is documented here.

   ⚑ flag

   Windows—none0/10

   The evidence pack contains no mention of Windows Clipboard History (Win+V) or unified clipboard sync across text/images; only unrelated features like Snap layouts, Copilot, and Windows Hello are documented. This is a fair capability for an OS to ship, but no supporting evidence is present.

   ⚑ flag

Theming

1. designerCreate a custom system theme using a GUI color and background picker

   weight 1 · round drawn
   Fedora Workstation—none0/10

   The evidence pack only shows dark mode/night light toggles and general desktop features; there is no mention of a GUI tool for creating custom system themes with color and background pickers, so this applicable axis lacks supporting evidence.

   ⚑ flag

   Windows—none0/10

   The evidence pack contains no mention of a GUI color/background picker or system theme customization tool for designers; only unrelated docs on app development, security, and general OS features are provided.

   ⚑ flag

2. power-userInstantly switch between multiple built-in visual themes that restyle the whole desktop

   weight 2 · round drawn
   Fedora Workstation—none0/10

   Evidence only shows a dark/light mode toggle and night light (fedora-docs-7), not multiple full desktop themes; community comments even note GNOME/Libadwaita requires extensions for basic customization rather than offering built-in theme switching (fedora-comm-4, fedora-comm-17). No evidence of instant switching between multiple built-in visual themes restyling the whole desktop.

   • [claimed-docs] “Flip a switch to turn on dark mode and give your eyes a break. Or use night light to reduce screen glare and help with sleep.”
   • [community] “Libadwaita is a horrible design language. It wastes so much space, the disparity between gtk3/4 hurts the eyes and you pretty much depend on…”
   • [community] “The fact that you need extensions for something as simple as dock functionality is insane... The fact that all my extensions get broken for …”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains no mention of built-in visual themes, dark/light mode switching, or desktop restyling features in Windows; only tangential docs on app development, Snap layouts, and unrelated community complaints are present.

   ⚑ flag

Accounts sync

1. switcherBring my online calendar, contacts, and data into the desktop with online account integration

   weight 2 · round to Fedora Workstation
   Fedora Workstation✓fullclaimed7/10

   Fedora's official docs explicitly state users can bring their online calendar, contacts, and data to the desktop via Online Accounts integration, matching the story directly. However, missing for 10: independent/hands-on corroboration of this specific feature, and no detail on which providers/services are supported or setup friction.

   • [claimed-docs] “Optionally, bring your online calendar, contacts and data to the desktop with online accounts.”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains no documentation of Windows features (e.g., Mail/Calendar/People apps, Microsoft Account contact/calendar sync) that let a switcher import online calendar, contacts, or data into the desktop. The only account-related evidence concerns friction with mandatory Microsoft Account sign-in (PIN requirement, truncated directory names) rather than data/calendar/contacts integration itself.

   • [community] “They have not removed it, it just is not visible by default if you are connected to the internet. Either run the setup without being connect…”
   • [community] “The online account is crap... I cannot even set a password, it asks me to set up a PIN number to log in.”
   • [community] “There is a long-standing Windows bug where local user directory names are created using a truncated version of the online account's name. Th…”

   proof ↗⚑ flag

Cross device continuity

1. power-userCopy content on one device and paste it on another paired device

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence of cross-device clipboard sync (e.g., GSConnect/KDE Connect integration or similar) is present in the pack; all evidence covers unrelated Workstation features and general community sentiment. Missing for 10: any mention of clipboard sharing, device pairing, or continuity features across devices.

   ⚑ flag

   Windows—none0/10

   No evidence pack items mention Windows Clipboard sync/Cloud Clipboard or cross-device paste features; only tangential docs on apps, security, and gaming are present.

   ⚑ flag

2. power-userStart a task on one device and finish it on another paired device

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence describes cross-device handoff/continuity features (e.g., syncing tasks, clipboard, or session state between paired devices); GNOME Online Accounts (fedora-docs-9) only syncs calendar/contacts data, not task continuity. Missing for 10: any documentation of device pairing, handoff, or continuity workflow across devices.

   • [claimed-docs] “Optionally, bring your online calendar, contacts and data to the desktop with online accounts.”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence of cross-device continuity features (e.g., Handoff-like task continuation, Cloud Clipboard, Phone Link continuity, timeline) in the provided pack; only unrelated app-dev, Snap layouts, security, and general community commentary are present.

   ⚑ flag

File sharing

1. power-userSend files wirelessly between nearby paired devices

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions wireless file sharing between paired devices (e.g., GNOME's Nautilus Send To/Warpinator/Nearby Sharing or similar). The axis is plausible for a desktop OS but entirely unevidenced here.

   ⚑ flag

   Windows—none0/10

   No evidence in the pack mentions Windows' Nearby Sharing feature or any wireless file-transfer capability between paired devices; only unrelated docs, accessibility, and gaming/UI features are covered.

   ⚑ flag

Localization

1. switcherUse the desktop in my own language thanks to community or official translations

   weight 1 · round to Fedora Workstation
   Fedora Workstation~partialclaimed5/10

   Fedora's official docs explicitly claim community translations make Workstation available in many languages, directly supporting the story. However, there is no detail on language coverage, translation completeness, or independent community corroboration confirming quality of the localization experience. Missing for 10: specifics on number/quality of supported languages, independent user reports confirming translation completeness, details on how to switch/select language.

   • [claimed-docs] “Thanks to a global community of translators, Workstation is available in many languages.”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains no mention of language packs, localization, or community/official translation support for the Windows desktop.

   ⚑ flag

Phone integration

1. power-userView and control my phone directly from my desktop

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence of any phone integration feature (e.g., GSConnect/KDE Connect) being documented or discussed for Fedora Workstation; the evidence pack covers VMs, containers, package management, and desktop UX but nothing about phone pairing or control.

   ⚑ flag

   Windows—none0/10

   No evidence in the pack mentions Phone Link, Your Phone app, or any feature allowing viewing/controlling a phone from the desktop; evidence covers app development, security, and unrelated community complaints.

   ⚑ flag

Cross platform dev

1. developerRun a full Linux terminal environment inside another host OS for development and tooling

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   The evidence pack covers Fedora Workstation's desktop features, virtualization (Boxes) and container tooling run on Fedora, but nothing addresses running Fedora itself as a Linux terminal environment inside another host OS (e.g., WSL-style integration or being packaged as a guest distro for Windows/macOS). Missing for 10: any mention of WSL support, cross-OS terminal integration, or official guest-environment packaging.

   ⚑ flag

   Windows✓fullcommunity7/10

   Community evidence explicitly confirms Windows Subsystem for Linux provides a functional, full Ubuntu terminal environment via syscall translation, which is exactly this developer story. However, the evidence pack lacks first-party Microsoft docs specifically on WSL setup/usage (the docs items here cover WinUI, Copilot, Store, etc., not WSL). Missing for 10: first-party WSL documentation citation, details on WSL2 kernel/distro management, and more recent independent corroboration beyond a single old HN thread.

   • [community] “I find it amazing that you can have such a functional Ubuntu environment by translating system calls... Microsoft calls it their 'Windows Su…”
   • [community] “Windows 10 is not bad at all, and I would have enjoyed keeping a Windows 10 machine handy with the new Ubuntu user land support.”

   proof ↗⚑ flag

2. developerUse the latest IDEs, toolchains, and AI/ML software on a primary supported platform

   weight 2 · round to Windows
   Fedora Workstation~partialclaimed5/10

   Fedora docs claim up-to-date packages/tools/runtimes and container tooling from Red Hat ecosystem, supporting a general 'latest software' story, but there is no specific evidence about AI/ML software availability, latest IDE support, or toolchain currency, and community comments focus on desktop/DE issues rather than dev tooling. missing for 10: explicit evidence of AI/ML framework support, IDE availability/updates, toolchain version currency, and independent corroboration of developer workflow claims.

   • [claimed-docs] “Use the latest container tools from the Red Hat ecosystem. No setup required. Access the Red Hat container registry.”
   • [claimed-docs] “All the packages, tools and runtimes you might need, up to date and ready for use with just a single command.”
   • [claimed-docs] “High-efficiency tools for creating, running and managing containers”

   proof ↗⚑ flag

   Windows~partialcommunity6/10

   Microsoft docs show first-party support for modern dev toolchains (Windows App SDK/WinUI 3, C#/.NET 8+, C++, Rust via windows-rs, MSIX packaging) and AI-specific tooling (Windows AI Foundry, Windows AI APIs for Copilot+ PCs), and community evidence confirms WSL provides a functional Linux dev environment on Windows. However, there's no direct evidence of support for widely-used third-party IDEs (VS Code, JetBrains) or major ML frameworks (PyTorch/TensorFlow/CUDA), and community reports raise reliability concerns (CrowdStrike-induced BSOD outage) that could affect dev workflows. Missing for 10: explicit IDE ecosystem coverage beyond Microsoft's own stack, ML/AI framework compatibility evidence, and independent corroboration of toolchain performance/stability for dev workloads.

   • [claimed-docs] “Build native Windows desktop apps with the Windows App SDK and WinUI 3, the recommended UI framework for new Windows apps.”
   • [claimed-docs] “Get started with Windows AI Foundry toolkit”
   • [claimed-docs] “Quickstart: Create and run a WinUI 3 project”
   • [claimed-docs] “Windows AI APIs for Copilot+ PCs”
   • [claimed-docs] “C# with .NET 8 or later, C++ (Win32 and C++/WinRT), Rust (via windows-rs crate). XAML is used for UI markup in WinUI 3 and WPF.”
   • [community] “I find it amazing that you can have such a functional Ubuntu environment by translating system calls... Microsoft calls it their 'Windows Su…”
   • [community] “I tried with Windows 10, and Windows Server 2019. Windows 2019 is super fast to set up and literally compiled the same c code in half the ti…”

   proof ↗⚑ flag

3. developerGet a full desktop developer experience running on low-cost single-board computers

   weight 1 · round drawn
   Fedora Workstation—none0/10

   No evidence pack items mention single-board computers (e.g., Raspberry Pi), ARM support, or a low-cost SBC developer image/spin; all evidence concerns general desktop features and community feedback on x86 desktop experience.

   ⚑ flag

   Windows—none0/10

   No evidence in the pack addresses Windows running on low-cost single-board computers (e.g., Raspberry Pi) or ARM-based SBC developer experience; all docs focus on standard desktop app development, UI frameworks, and general Windows features unrelated to SBC hardware support.

   ⚑ flag

Dev environment

1. developerUse container tools out of the box with no additional setup required

   weight 2 · round to Fedora Workstation
   Fedora Workstation✓fullclaimed7/10

   Fedora Workstation's own docs explicitly claim container tools come pre-configured with no setup required, including registry access and up-to-date runtimes ready with a single command. Missing for 10: independent/hands-on corroboration of the no-setup claim and details on which container runtime (Podman/Toolbx) is preinstalled vs requiring extra install.

   • [claimed-docs] “Use the latest container tools from the Red Hat ecosystem. No setup required. Access the Red Hat container registry.”
   • [claimed-docs] “All the packages, tools and runtimes you might need, up to date and ready for use with just a single command.”
   • [claimed-docs] “High-efficiency tools for creating, running and managing containers”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence pack items mention Docker, containers, WSL2 container integration, or any out-of-the-box container tooling for Windows; documentation focuses on WinUI/app development, Store submission, and general OS features. Missing for 10: any mention of built-in container runtime, Docker Desktop bundling, or container CLI shipped by default.

   ⚑ flag

2. developerQuickly set up preconfigured development environments for popular frameworks and languages

   weight 2 · round drawn
   Fedora Workstation~partialclaimed4/10

   Fedora Workstation provides generic building blocks—up-to-date runtimes/packages via a single command, container tooling from the Red Hat ecosystem, and Boxes for spinning up VMs—but there's no evidence of curated, ready-made environment templates for specific frameworks/languages (e.g., one-click Node/Python/Java dev stacks or devcontainer-style presets). Community evidence is generic distro sentiment, not about dev environment setup specifically. Missing for 10: language/framework-specific preconfigured environment templates, first-party dev-container or toolbx presets, and independent hands-on evidence of quick framework setup.

   • [claimed-docs] “Boxes takes the guesswork out of using virtual machines. Just select the OS you want to install, and the app will do the rest.”
   • [claimed-docs] “Use the latest container tools from the Red Hat ecosystem. No setup required. Access the Red Hat container registry.”
   • [claimed-docs] “All the packages, tools and runtimes you might need, up to date and ready for use with just a single command.”
   • [claimed-docs] “High-efficiency tools for creating, running and managing containers”

   proof ↗⚑ flag

   Windows~partialcommunity4/10

   Windows docs show support for major languages/frameworks (C#, .NET, C++, Rust, WinUI) and community evidence confirms WSL lets developers spin up a full Linux userland (e.g., Ubuntu) for cross-platform dev work, which counts as an OS-level way to get a preconfigured environment. However there's no evidence of a dedicated 'quick setup' tool (e.g., Dev Home, winget dev environment configs, dev containers) that packages a full preconfigured stack for popular frameworks. Missing for 10: dedicated dev-environment provisioning tool/docs (Dev Home, winget manifests, devcontainer support), first-party quickstart tutorials for multiple frameworks beyond WinUI, and independent hands-on confirmation of setup speed.

   • [claimed-docs] “C# with .NET 8 or later, C++ (Win32 and C++/WinRT), Rust (via windows-rs crate). XAML is used for UI markup in WinUI 3 and WPF.”
   • [community] “I find it amazing that you can have such a functional Ubuntu environment by translating system calls... Microsoft calls it their 'Windows Su…”
   • [community] “Windows 10 is not bad at all, and I would have enjoyed keeping a Windows 10 machine handy with the new Ubuntu user land support.”
   • [claimed-docs] “Quickstart: Create and run a WinUI 3 project”

   proof ↗⚑ flag

3. developerGet a full set of packages, tools, and runtimes ready to use with a single command

   weight 3 · round to Fedora Workstation
   Fedora Workstation~partialcommunity6/10

   First-party docs explicitly claim 'all the packages, tools and runtimes... ready for use with just a single command' plus container tooling and easy package management, directly matching the story. However, there's no independent/hands-on corroboration of this specific claim, and community evidence about package/app installation friction (e.g. needing extra steps for certain apps, Flatpak complaints) raises some doubt about the seamlessness. Missing for 10: independent verification of the 'single command' setup claim, and details on which runtimes/languages are included out of the box.

   • [claimed-docs] “All the packages, tools and runtimes you might need, up to date and ready for use with just a single command.”
   • [claimed-docs] “Easily install, update and manage software packages”
   • [claimed-docs] “High-efficiency tools for creating, running and managing containers”
   • [community] “I chose popos, because the second I wanted discord or Spotify on fedora I had to go through a whole page of commands to do it, and it didn't…”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack has no mention of winget, Windows Package Manager, Dev Home, or any single-command bootstrap for installing packages/tools/runtimes; it only covers app development frameworks (WinUI, Windows App SDK) and PowerShell as a scripting CLI, none of which describe a one-command full dev environment setup. missing for 10: evidence of winget/package manager, evidence of a documented single-command install of packages/tools/runtimes, any dev-environment bootstrap tool.

   • [claimed-docs] “C# with .NET 8 or later, C++ (Win32 and C++/WinRT), Rust (via windows-rs crate). XAML is used for UI markup in WinUI 3 and WPF.”
   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/powershell/scripting/overview”

   proof ↗⚑ flag

4. developerQuickly create and run virtual machines without manual configuration

   weight 2 · round to Fedora Workstation
   Fedora Workstation~partialclaimed5/10

   Fedora Workstation ships GNOME Boxes, which per docs lets users select an OS and have the app handle VM creation without manual configuration, directly matching the story. However, evidence is limited to a single vendor marketing line with no independent/hands-on corroboration of ease-of-use, speed, or developer workflow specifics (e.g., CLI/automation, snapshotting, networking). missing for 10: independent/hands-on validation of Boxes VM creation experience, details on developer-specific workflows (scripting, cloud-init, snapshots), and comparison to manual libvirt/virt-manager setup.

   • [claimed-docs] “Boxes takes the guesswork out of using virtual machines. Just select the OS you want to install, and the app will do the rest.”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence pack items discuss Hyper-V, WSL VM creation, or any tooling for quickly spinning up virtual machines without manual configuration; the docs cover UI frameworks, app packaging, and general OS features instead. This is a fair axis for an OS/dev platform, but absence of relevant evidence means it is not shown to be delivered.

   ⚑ flag

Gpu drivers

1. developerInstall GPU vendor drivers and build custom kernel modules for accelerated workloads

   weight 2 · round to Fedora Workstation
   Fedora Workstation~partialcommunity3/10

   Community anecdotes show mixed results: one user reports Nvidia suspend now works on Fedora (implying successful driver install) while another calls Nvidia drivers their 'biggest complaint' and a third cites missing CUDA support as a blocker for professional use. There is no first-party documentation on installing GPU vendor drivers or building custom kernel modules (e.g., akmod/dkms), and no evidence at all about kernel module compilation workflows. missing for 10: official docs on GPU driver installation, evidence of kernel-module build tooling (akmod/dkms), and consistent positive outcomes rather than mixed anecdotal reports.

   • [community] “Fedora 39 KDE Spin has been flawless so far, and I love the window tiling native support. Also, suspend on Nvidia works again for me.”
   • [community] “I've tried a variety of linucies, but I keep coming back to Fedora. It frequently works the best 'out of the box'... My biggest complaint is…”
   • [community] “Unfortunately I cannot switch to Fedora on my desktop, mainly because of lack of support of Adobe, missing 10bit support and CUDA. Linux is …”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence in the pack addresses GPU driver installation or kernel-mode driver development (WDK, DDI, signing) for Windows; the docs focus on app development frameworks (WinUI, MSIX) and consumer features, not device driver/kernel module tooling.

   ⚑ flag

Power performance

1. power-userInstall and use the OS without vendor lock-in on hardware of my choosing

   weight 1 · round to Fedora Workstation
   Fedora Workstation~partialcommunity5/10

   Fedora is a free, open-source distro that can be installed on generic x86 hardware without vendor tie-in, and community reports confirm it 'works best out of the box' on varied hardware (fedora-comm-6), but the same threads flag real hardware friction—NVIDIA driver/suspend issues, Wi‑Fi problems, and Wayland breaking on older machines (fedora-comm-6, fedora-comm-8, fedora-comm-19)—showing hardware freedom is not friction-free. Missing for 10: explicit vendor documentation on hardware certification/compatibility lists, ARM/other-architecture support claims, and independent benchmarks confirming broad hardware compatibility beyond anecdotal forum comments.

   • [community] “I've tried a variety of linucies, but I keep coming back to Fedora. It frequently works the best 'out of the box'... My biggest complaint is…”
   • [community] “only Arch seems to be the smoothest. I'm running EndeavourOS... Fedora always freezes for minutes when the RAM is full. I'm thinking maybe i…”
   • [community] “Unfortunately I cannot switch to Fedora on my desktop, mainly because of lack of support of Adobe, missing 10bit support and CUDA. Linux is …”
   • [community] “Although Wayland is more modern, it's been nothing but trouble for me on older hardware. I'd prefer non-smooth scrolling any day over a comp…”

   proof ↗⚑ flag

   Windows!disputedcontradicted4/10

   Windows docs claim broad hardware/device compatibility (windows-docs-10, windows-docs-11) suggesting freedom of hardware choice, but community evidence shows Microsoft has been increasingly forcing a Microsoft Account sign-in (hiding the local-account option, requiring workarounds like disconnecting from the internet) and bundling mandatory telemetry/updates, which is a form of vendor lock-in that contradicts the 'no lock-in' framing (windows-comm-6, windows-comm-7, windows-comm-8, windows-comm-11). Missing for 10: clear first-party documentation of unrestricted local-account/offline install options, and no independent confirmation that hardware freedom extends to full account/software independence.

   • [claimed-docs] “Works with your apps and accessories”
   • [claimed-docs] “Yes, most applications, devices, and accessories that worked with Windows 10 are compatible with Windows 11.”
   • [community] “They have not removed it, it just is not visible by default if you are connected to the internet. Either run the setup without being connect…”
   • [community] “The online account is crap... I cannot even set a password, it asks me to set up a PIN number to log in.”
   • [community] “Before Nadella, Windows wasn't nearly as user-hostile as it is now. There was no mandatory telemetry, there were no forced updates... now th…”
   • [community] “Tracking and privacy on Windows is becoming atrocious, I didn't know about the built-in keylogger until I ran a declutter tool.”

   proof ↗⚑ flag

2. power-userGet better performance and extended device lifespan by installing the OS on older hardware

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No vendor documentation claims Fedora Workstation is optimized for older hardware or extends device lifespan; the only performance-related docs item is a generic 'performance mode' toggle unrelated to legacy hardware. Community evidence actually reports the opposite experience, with fedora-comm-19 stating Wayland has been 'nothing but trouble... on older hardware' and fedora-comm-8 noting freezes under RAM pressure, so there's no support for this specific story.

   • [claimed-docs] “Use performance mode to boost hardware speed when you need it.”
   • [community] “Although Wayland is more modern, it's been nothing but trouble for me on older hardware. I'd prefer non-smooth scrolling any day over a comp…”
   • [community] “only Arch seems to be the smoothest. I'm running EndeavourOS... Fedora always freezes for minutes when the RAM is full. I'm thinking maybe i…”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains no documentation about installing Windows on older/legacy hardware to improve performance or extend device lifespan; all hardware-related items focus on compatibility with current devices, biometric login, or Copilot+ PC AI features rather than support for aging hardware. Windows 11's known strict hardware requirements (TPM, CPU generation) are not addressed here either way, so there is no evidence this capability is delivered.

   ⚑ flag

3. power-userBoost hardware performance on demand using a performance mode toggle

   weight 1 · round to Fedora Workstation
   Fedora Workstation✓fullclaimed7/10

   Fedora Workstation explicitly documents a performance mode toggle to boost hardware speed on demand, directly matching the story. Missing for 10: independent hands-on verification or details on which hardware/settings it affects, and no community corroboration of its real-world effectiveness.

   • [claimed-docs] “Use performance mode to boost hardware speed when you need it.”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains no documentation of Windows power plans, the performance/battery slider, Game Mode, or any explicit performance-mode toggle; windows-docs-8 only vaguely states the OS targets 'power users with high-performance hardware needs' without describing a toggle mechanism. This is a fair axis for an OS to be judged on, but no concrete capability evidence is present, so it defaults to none.

   • [claimed-docs] “Audience: Power users with high-performance hardware needs”

   proof ↗⚑ flag

Remote access

1. power-userShare my desktop remotely or access a remote desktop session from my machine

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions remote desktop sharing, screen sharing, VNC/RDP support, or GNOME Remote Desktop features; the docs focus on VMs, containers, app installation, and UI features unrelated to remote desktop access. This is an applicable axis for a desktop OS but no evidence supports it. missing for 10: any mention of remote desktop sharing tools, VNC/RDP client or server capability, or GNOME Remote Desktop/Connections features.

   ⚑ flag

   Windows—none0/10

   No evidence pack item mentions Remote Desktop, Quick Assist, or any remote-desktop/screen-sharing feature; the pack covers app development, UI, security, and unrelated community complaints. Windows is well known to include Remote Desktop, but per the rules absence of evidence in the pack must be judged as none.

   ⚑ flag

Accessibility

1. switcherUse built-in screen readers and accessibility tools to get started with the OS

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence pack item mentions screen readers, accessibility tools (e.g., Orca), high-contrast mode, or any assistive technology features; only tangential UX items like dark mode/night light are present. Missing for 10: any mention of screen reader support, accessibility settings panel, keyboard navigation aids, or assistive tech onboarding.

   ⚑ flag

   Windows~partialclaimed4/10

   Evidence only shows a Live Captions accessibility feature mention; there's no documentation of built-in screen readers (Narrator), Magnifier, or a dedicated setup/onboarding accessibility flow for switchers. Missing for 10: mention of Narrator/screen reader, accessibility settings during OOBE/setup, and independent corroboration of accessibility usability for new users.

   • [claimed-docs] “Turn on Live Captions”

   proof ↗⚑ flag

First install

1. switcherCreate bootable installation media and install the OS from a USB stick

   weight 3 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions creating bootable USB media or the installation process; all citations concern desktop features (Boxes, containers, software store) or general community opinions unrelated to installation media. missing for 10: documentation on media creation tools (e.g. Fedora Media Writer), USB install instructions, boot process, and any confirmation of successful installs from USB.

   ⚑ flag

   Windows—none0/10

   No evidence in the pack addresses creating bootable USB installation media (e.g., Media Creation Tool, Rufus, ISO download) or performing a clean install from USB; all docs cover app development, features, and support topics unrelated to install-setup media creation.

   ⚑ flag

2. switcherInstall the OS alongside my existing OS in a dual-boot configuration

   weight 3 · round drawn
   Fedora Workstation—none0/10

   The evidence pack contains no mention of installer options, partitioning, dual-boot support, or coexistence with another OS; all cited docs cover desktop features (containers, apps, VMs) and community comments unrelated to installation setup. This is an applicable axis for an OS product, but no evidence supports it. Missing for 10: any documentation or community report about the Anaconda installer's dual-boot/partitioning support, coexistence with Windows/other OS, or bootloader handling.

   ⚑ flag

   Windows—none0/10

   No evidence pack items mention dual-boot installation, partitioning alongside another OS, or bootloader/multi-boot setup guidance; the evidence covers app development, features, and community sentiment unrelated to install-setup dual-boot scenarios.

   ⚑ flag

3. switcherFollow guided tutorials to install the OS and learn the desktop interface

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   The evidence pack describes desktop features and marketing copy (search, dark mode, app installation) but contains no guided tutorial, onboarding walkthrough, or installation-learning content aimed at switchers; community items are general opinions/bugs unrelated to tutorials.

   ⚑ flag

   Windows~partialcommunity3/10

   Microsoft support docs cover feature-specific help (PC Health Check, BitLocker key backup, desktop features like Snap layouts, Windows Hello) which could help a new user learn parts of the desktop, but there is no evidence of a dedicated 'switcher' onboarding tutorial or step-by-step OS installation guide; community threads even note setup friction (forced Microsoft account, PIN-only login) rather than smooth guided onboarding. missing for 10: a first-party switcher/install walkthrough, a structured 'learn the desktop' tutorial series, and independent confirmation such tutorials work well for new users.

   • [claimed-docs] “How to use the PC Health Check app”
   • [claimed-docs] “Back up your BitLocker recovery key”
   • [claimed-docs] “organize windows on your screen with Snap layouts and create Snap groups to hop back into”
   • [community] “They have not removed it, it just is not visible by default if you are connected to the internet. Either run the setup without being connect…”
   • [community] “The online account is crap... I cannot even set a password, it asks me to set up a PIN number to log in.”

   proof ↗⚑ flag

4. switcherInstall the OS in place of my current OS on the same machine

   weight 2 · round drawn
   Fedora Workstation—none0/10

   The evidence pack contains only marketing feature bullets (Boxes, containers, dark mode, search, app store) and general community sentiment about desktop experience, but nothing about the installer, disk partitioning, or replacing an existing OS on the same machine. Missing for 10: any documentation or hands-on account of the Fedora installer, dual-boot/erase-disk options, or a switcher successfully replacing another OS.

   ⚑ flag

   Windows—none0/10

   The evidence pack contains no documentation or community reports about installing Windows in place of an existing OS (e.g., clean install, dual-boot, replacing another OS on hardware); only tangential items like PC Health Check upgrade eligibility appear. missing for 10: installation media/USB creation, clean-install walkthrough, dual-boot or OS-replacement guidance, hands-on switcher reports of successful in-place installation.

   • [claimed-docs] “How to use the PC Health Check app”

   proof ↗⚑ flag

Migration

1. switcherTransfer my files and settings from my old computer to a new machine running the OS

   weight 3 · round drawn
   Fedora Workstation—none0/10

   No evidence pack item mentions a migration/import tool, transfer wizard, or settings-sync feature for switchers; only unrelated GNOME desktop features and general community opinions are present.

   ⚑ flag

   Windows—none0/10

   No evidence in the pack mentions a migration/transfer tool (e.g., PC-to-PC transfer, OneDrive settings sync, or a 'Windows Backup' migration feature) for moving files and settings from an old computer to a new one; the pack only covers app development, security, and general feature marketing.

   ⚑ flag

Recovery

1. power-userRoll back the system to a previous snapshot if an update breaks something

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence pack item mentions snapshots, Btrfs rollback, OSTree/Silverblue image rollback, or any update-rollback mechanism for Fedora Workstation; the docs excerpts cover apps, containers, VMs, and desktop features but not system rollback.

   ⚑ flag

   Windows~partialcommunity3/10

   The only evidence touching on system rollback is a community anecdote about using 'F8 + last known good configuration' to recover from a boot loop during the CrowdStrike outage, not vendor documentation of System Restore, restore points, or snapshot rollback features. Missing for 10: first-party docs on System Restore/restore points, instructions for creating/using snapshots, and independent confirmation that rollback reliably fixes update-caused issues.

   • [community] “'F8 + last known good configuration' worked for us to recover from the boot loop.”
   • [community] “A CrowdStrike update caused global Windows BSODs and boot loops, taking down businesses, banks, airlines, hospitals and 911 services worldwi…”

   proof ↗⚑ flag

1. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Fedora Workstation—none0/10

   The evidence pack contains only marketing feature descriptions and community sentiment about UX/performance; none of it addresses source code availability, licensing, or repository access, so there is no evidence Fedora Workstation's source is documented as open-licensed within this pack.

   ⚑ flag

   Windows—none0/10

   Windows is closed-source proprietary software; no evidence in the pack indicates any open-license source availability, and the axis clearly applies since source openness is a fair question for any software product.

   ⚑ flag

1. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence pack items mention telemetry, usage tracking, or opt-out settings for Fedora Workstation; all citations concern unrelated features (VMs, containers, dark mode) or general community sentiment about desktop environments. This is a fair question for an OS product, but absence of any evidence means it cannot be credited.

   ⚑ flag

   Windows—none0/10

   No first-party documentation in the evidence pack describes a telemetry opt-out mechanism, and community reports explicitly state telemetry became mandatory and non-optional under Windows, with no way to fully disable it. This is an applicable axis for any OS but the evidence shows no delivered opt-out capability.

   • [community] “Before Nadella, Windows wasn't nearly as user-hostile as it is now. There was no mandatory telemetry, there were no forced updates... now th…”
   • [community] “Tracking and privacy on Windows is becoming atrocious, I didn't know about the built-in keylogger until I ran a declutter tool.”
   • [community] “I always thought Windows did a lot of stuff well (when it was good at least). The telemetry, changing things for the sake of changing things…”

   proof ↗⚑ flag

Authentication

1. power-userManage passwords and passkeys using a built-in privacy and security tool

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence pack item mentions a password manager, GNOME Keyring/Secrets app, passkey support, or any built-in credential management tool; the evidence covers unrelated Workstation features (Boxes, containers, software center, dark mode, etc.).

   ⚑ flag

   Windows~partialclaimed4/10

   Windows Hello is documented as a built-in biometric/PIN sign-in system replacing passwords (windows-docs-9, windows-docs-12) and Windows 11 Pro touts 'latest credential safeguards' including Windows Hello for Business (windows-docs-20), showing some built-in credential/security tooling. However, there is no explicit evidence of a dedicated passkey manager UI or Credential Manager for viewing/editing saved passwords and passkeys. Missing for 10: explicit documentation of a Credential Manager/passkey management interface, evidence of passkey creation/storage workflow, and independent confirmation it works as a full password+passkey manager.

   • [claimed-docs] “Log in with your face, fingerprint, or PIN using Windows Hello”
   • [claimed-docs] “No need to remember or type your password. Log in with your face, fingerprint, or PIN using Windows Hello”
   • [claimed-docs] “Defend against cyberthreats with the latest credential safeguards for better peace of mind, including biometric sign-in with Windows Hello f…”

   proof ↗⚑ flag

Disk encryption

1. switcherI get full-disk encryption enabled automatically without manual security setup

   weight 3 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions disk encryption, LUKS, or any automatic security setup during installation; all evidence covers unrelated features (VMs, containers, dark mode, community opinions on desktop environments).

   ⚑ flag

   Windows—none0/10

   The only relevant evidence is a support doc telling users to back up their BitLocker recovery key, which implies encryption setup requires user action rather than being fully automatic with zero manual steps; there's no documentation showing device encryption turns on automatically for switchers without any configuration. missing for 10: evidence of automatic BitLocker/Device Encryption activation on install, hardware requirements/limitations, and confirmation no manual steps are needed.

   • [claimed-docs] “Back up your BitLocker recovery key”

   proof ↗⚑ flag

2. power-userEncrypt my disk using TPM-backed hardware encryption

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence in the pack mentions disk encryption, LUKS, or TPM-backed encryption at all; the evidence pack only covers unrelated Workstation features and general community sentiment.

   ⚑ flag

   Windows~partialclaimed4/10

   The pack only references BitLocker via a support note on backing up the recovery key, implying disk encryption exists, but never documents TPM-backed hardware encryption specifics, setup steps, or hardware requirements. Missing for 10: explicit TPM binding details, setup/config instructions, device encryption vs BitLocker distinction, and independent hands-on verification.

   • [claimed-docs] “Back up your BitLocker recovery key”

   proof ↗⚑ flag

Network security

1. switcherI get a default firewall enabled automatically without manual configuration

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions a firewall, firewalld, or any default network security configuration for Fedora Workstation; all cited docs focus on apps, containers, UI features, and unrelated community commentary.

   ⚑ flag

   Windows—none0/10

   The evidence pack contains no mention of Windows Defender Firewall or any default firewall behavior, only unrelated topics like app development, security credentials, and community complaints about telemetry/updates. Missing for 10: any documentation or evidence that Windows Firewall is enabled by default out-of-box, its configuration state, or user reports confirming automatic protection.

   ⚑ flag

Update lifecycle

1. power-userEnable extended years of security update coverage on my installation

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions extended support releases, LTS options, or extended security update coverage for Fedora Workstation (Fedora's standard support is ~13 months per release with no documented extended-support tier). The axis applies since a Linux distro could plausibly offer such a program, but nothing here demonstrates it.

   ⚑ flag

   Windows—none0/10

   The evidence pack contains no mention of Windows Extended Security Updates (ESU) enrollment or any mechanism for power-users to extend security update coverage beyond standard support; only a passing community remark about Windows 10 eventually losing updates (windows-comm-14) touches the topic without describing any enablement path.

   • [community] “In couple of years Windows 10 will get eol'd and stop receiving security updates... I expect to see additional influx of new Linux users fro…”

   proof ↗⚑ flag

Multi device display

1. designerUse a paired tablet device as a secondary display for creative apps

   weight 2 · round drawn
   Fedora Workstation—none0/10

   No evidence in the pack mentions tablet-as-secondary-display, screen extension, or any related feature; the evidence pack covers unrelated Workstation features and general community sentiment. This is a fair window-management/creative-workflow question for a desktop OS, but nothing shows Fedora delivers it.

   ⚑ flag

   Windows—none0/10

   The evidence covers Snap layouts, tablet/laptop mode switching, and general app compatibility, but there is no mention of a feature letting a paired tablet act as a secondary/extended display for creative apps (e.g., a Sidecar-like capability). Missing for 10: any documentation of wireless/paired secondary-display extension to a tablet, creative-app-specific pairing support, or independent confirmation of such a feature.

   • [claimed-docs] “organize windows on your screen with Snap layouts and create Snap groups to hop back into”
   • [claimed-docs] “Switch easily from tablet to laptop—and back—to work the way that you prefer.”
   • [claimed-docs] “Works with your apps and accessories”

   proof ↗⚑ flag

Navigation

1. power-userSearch for files, apps, and settings instantly from a global search launcher

   weight 3 · round to Fedora Workstation
   Fedora Workstation✓fullclaimed7/10

   Fedora docs explicitly confirm the GNOME Activities search launcher ('Press the Super key and just type to search for what you need'), which searches files, apps, and settings from one global launcher. Missing for 10: no independent/hands-on corroboration of search speed or scope (files vs settings vs apps) beyond the vendor description.

   • [claimed-docs] “Press the Super key and just type to search for what you need.”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains nothing about Windows Search, the Start menu search box, or any global search launcher for files/apps/settings — only window-snapping, Copilot, security, and app-development docs are present. Missing for 10: any first-party documentation or community confirmation of the global search launcher feature itself.

   ⚑ flag

2. power-userOperate the entire system using only the keyboard via hotkeys and a launcher

   weight 3 · round to Fedora Workstation
   Fedora Workstation~partialclaimed3/10

   The only evidence is the GNOME Activities/Super-key search-and-launch feature, which supports keyboard-driven app launching but says nothing about hotkey-driven window management, tiling, or entire-system keyboard navigation. Missing for 10: documentation of keyboard shortcuts for window snapping/tiling/workspace switching, evidence of full keyboard-only operability without mouse fallback, and any independent hands-on confirmation of keyboard-centric workflows.

   • [claimed-docs] “Press the Super key and just type to search for what you need.”

   proof ↗⚑ flag

   Windows—none0/10

   The evidence pack contains no documentation of keyboard-only operation, system-wide hotkeys, or a launcher (e.g., Start menu search, Run dialog, PowerToys Run) for window/app control; only Snap layouts (mouse-oriented) and PowerShell CLI are mentioned, neither of which addresses full keyboard-driven navigation. Missing for evidence: hotkey reference documentation, launcher/search functionality docs, keyboard navigation accessibility guides.

   ⚑ flag

3. power-userSnap and tile windows into predefined layouts for multitasking

   weight 2 · round to Windows
   Fedora Workstation—none0/10

   No evidence describes Fedora Workstation (GNOME) shipping predefined tiling/snap layouts; the only tiling praise found (fedora-comm-5) refers to the separate KDE Spin, not Workstation itself, so it cannot support this claim.

   ⚑ flag

   Windows✓fullclaimed7/10

   Windows docs explicitly describe Snap layouts and Snap groups for organizing windows on screen and returning to grouped tasks, directly matching the story. Missing for 10: no independent/hands-on corroboration of Snap layout customization or reliability, and no detail on how many predefined layouts or keyboard shortcuts are available.

   • [claimed-docs] “organize windows on your screen with Snap layouts and create Snap groups to hop back into”

   proof ↗⚑ flag

Notifications

1. power-userSilence notifications using a Do Not Disturb mode

   weight 2 · round to Fedora Workstation
   Fedora Workstation✓fullclaimed7/10

   Fedora Workstation's docs explicitly state 'Turn off notifications with Do Not Disturb,' directly matching the story. Missing for 10: independent/hands-on corroboration of the feature and details on configuration options beyond the single doc line.

   • [claimed-docs] “Turn off notifications with Do Not Disturb.”

   proof ↗⚑ flag

   Windows—none0/10

   No evidence in the pack mentions Windows Focus Assist / Do Not Disturb notification silencing features; nothing in the docs or community items addresses this capability.

   ⚑ flag