France to ditch Windows for Linux to reduce reliance on US tech

Original Article ↗ Hacker News Discussion ↗

Motivations and Sovereignty

  • Many see the move as a strategic response to dependence on US tech, similar to reducing reliance on Russian energy.
  • Concerns include the CLOUD Act, US sanctions history, and political instability, making US platforms a sovereignty and security risk.
  • Some argue this should have happened decades ago; others note repeated back-and-forth in France and Germany due to lobbying and inertia.
  • There is frustration that “digital sovereignty” talk often doesn’t translate into actual support for existing open‑source European projects.

Feasibility of Migrating to Linux

  • Broad agreement that most government users mainly need a browser, email, and office suite; Linux is seen as adequate or superior here.
  • Power‑user and “edge case” concerns: complex Excel macros/VBA, niche desktop apps, specialized CAD (e.g., CATIA/SolidWorks) and media tools.
  • Some argue you must go “100% in” to avoid Windows becoming a status symbol and undermining the migration; others suggest 80–90% coverage is already a major win.

Enterprise Management and AD/Group Policy

  • A major technical barrier cited is lack of a Linux equivalent to Windows’ Active Directory + Group Policy + Intune/Entra ecosystem.
  • Counter‑arguments: Linux already has building blocks (FreeIPA/IdM, Samba AD, config management like Ansible/Puppet, dconf/KDE kiosk, AppArmor/SELinux).
  • Debate over whether a Windows‑style central policy layer is desirable, or whether Linux’s more scriptable, decentralized model is actually better.

Desktop Linux Maturity

  • Many report using Linux as a daily driver for years; Windows is described as increasingly ad‑heavy, locked down, and unreliable (sleep, updates).
  • Others emphasize Linux’s UX inconsistency and hardware quirks (multi‑monitor, Wi‑Fi, drivers), arguing it’s still not “friction‑free” for non‑technical staff.
  • Some worry that mass adoption will attract “enshittification” and bureaucracy into the Linux ecosystem itself.

Mobile, Cloud, and Hardware Gaps

  • Several note that true independence also needs a sovereign mobile OS and cloud; AOSP forks, Sailfish, Jolla, /e/OS, and Linux-on-mobile are mentioned but seen as immature or partially proprietary.
  • Hardware sovereignty is considered far harder (globalized supply chains, ASML bottleneck), with consensus that software decoupling is the nearer‑term goal.

Outlook and Skepticism

  • Optimists see this as a serious, security‑driven shift; pessimists call it bargaining leverage with Microsoft or another doomed “LiMux‑style” experiment.
  • Many stress that success hinges on sustained funding, professional execution, and real collaboration with existing open‑source projects, not state‑built one‑offs.