Linux Part 3: AI-Powered Learning, Post-Ubuntu Distros, Actually existing DE's, App Packaging&Delivery Approaches

Linux Part 3: AI-Powered Learning, Post-Ubuntu Distros, Which DE Actually Exist, App Packaging&Delivery Approaches

This is a continuation of the Linux intro series. If you haven't read Parts 1 and 2, start there - this assumes you understand basic Linux concepts like the FHS, package managers, and configuration management.

The Ubuntu Reality Check

Ubuntu has a reputation as the "beginner-friendly" distro. And it was - back in 2010. But here's the uncomfortable truth: Ubuntu's "simplifications" now create more problems than they solve.

You've already experienced this firsthand with your GPG key nightmares and library version conflicts. These aren't random bugs - they're symptoms of Ubuntu's architectural decisions.

The Problems With "User-Friendly" Ubuntu

Snap and Flatpak bloat:

• Install 3 applications → They consume 50 GB of disk space
• Performance is measurably slower than native packages
• Updates happen separately from your system updates
• Flatpak's hype died in 2022-2023 - if you need portability, use AppImage instead

Repository fragmentation:

• Nearly every application requires manually adding a new repository
• Each repository needs its own GPG key (hence your pain)
• This creates a tangled web of trust relationships
• Updates can break when repos become incompatible

"GUI for everything" isn't unique anymore:

• In 2010, avoiding the terminal was Ubuntu's killer feature
• In 2025, virtually every major distro has excellent GUI tools
• You've already learned the terminal basics - you don't need Ubuntu to protect you from it

The library version hell:

• Ubuntu holds packages at specific versions for "stability"
• Newer software often needs newer libraries
• You end up manually managing dependencies (remember trying to remove Wine libraries?)
• This problem is architecturally impossible on rolling-release distros

What You Did Right

Focusing on one distro - Absolutely correct. Distro-hopping teaches you nothing. You learn the system by living with it through problems and solutions.

But you picked Ubuntu because of outdated advice. Let's fix that.

The Real Linux Landscape

Here's the truth: There are only 3 distros. Everything else is a derivative or niche project.

1. Ubuntu - Debian-based, corporate-backed, "stable" releases
2. Fedora - Red Hat-based, cutting-edge, 6-month release cycle
3. Arch - Rolling release, bleeding edge, community-driven

Pick your base. Everything else (Mint, Pop!_OS, Manjaro, etc.) is just someone's pre-configured version of one of these three.

Why Arch (Via EndeavourOS)

I'm recommending EndeavourOS - which is Arch with:

• Graphical installer (no command-line installation dance)
• Automatic driver detection and installation
• Sensible defaults pre-configured
• But it's still pure Arch under the hood

The Practical Benefits

Single, unified repository:

• No PPA hell
• No manual GPG key management
• Everything comes from one source (pacman) or the community (AUR)
• Your "which repo has this package?" question never comes up

Up-to-date packages:

• New software versions arrive within days
• Libraries update alongside programs
• That Windows program that needs Wine 8.x? You have it already

The Arch Wiki:

• Seriously, this alone justifies using Arch
• Updated daily by the community
• Every problem you'll encounter has a wiki page
• Clear, technical, no-nonsense documentation
• Example: wiki.archlinux.org - bookmark this

Fast package manager:

• pacman is significantly faster than apt
• AUR helper (yay) makes community packages feel native
• Update your entire system: yay (just that, one command)

The "Arch Breaks on Updates" Myth

Reality: 90% myth, 10% minor inconveniences.

Here's what actually happens:

• Small issues occur every few months
• Fixes appear within 0-7 days
• You check the Arch homepage before major updates
• If there's a known issue, you wait a day or two

Your Ubuntu experience was worse:

• GPG key failures
• Trying to manually manage library dependencies
• Repository version mismatches

On Arch, these problems structurally cannot happen because of the rolling release model and unified repository.

The Desktop Environment Question

Forget the 15 different desktop environments. There are only 2 that matter:

1. GNOME - Opinionated, keyboard-workflow focused, "our way or the highway"
2. KDE Plasma - Flexible, traditional desktop, infinitely customizable

Everything else (XFCE, Cinnamon, MATE, etc.) is either a fork of these two or a niche project.

You're on KDE already - good choice. It's the Windows-like experience done right. Keep it.

Learning Resources: Stop Googling

You mentioned Google is inefficient for learning Linux. You're absolutely right.

Use AI, Not Search Engines

Instead of Googling "how to install X on Linux":

Ask ChatGPT/Claude/DeepSeek:
"I'm on Arch Linux with KDE. I want to install [program]. 
What's the best way, and what should I know about it?"

You'll get:

• Step-by-step instructions
• Context about why you're doing each step
• Warnings about common pitfalls
• Alternative approaches

Google gives you: 10 outdated forum posts from 2015, half for the wrong distro.

Essential Websites (Not Google)

AlternativeTo.net - Finding Linux replacements for Windows programs

• Search for your Windows app
• Filter by "Linux"
• See ratings, reviews, and actual user experiences

appdb.winehq.org - Checking Windows software compatibility with Wine

• Search the program
• See tested versions and what works/breaks
• Community workarounds

DistroWatch.com - The distro leaderboard

• Popularity rankings (with context)
• Distro family trees
• News about releases and changes

portablebspps.com - Finding portable Windows apps

• Many installers break under Wine
• Portable versions often work flawlessly
• Skip the installer entirely

Gaming and Graphics: Real Talk

Forcing GPU Selection

For NVIDIA users (if you have hybrid graphics):

# Force NVIDIA for any program
__GLX_VENDOR_LIBRARY_NAME=nvidia program_name

# Force NVIDIA for Wine/Proton games
__GLX_VENDOR_LIBRARY_NAME=nvidia wine game.exe

This is way simpler than Windows's clunky NVIDIA Control Panel per-application settings.

PortProton Is Unnecessary

You don't need PortProton. Here's why:

What you actually need:

• Steam (in the official repos)
• Steam Runtime (included with Steam)
• That's it

Steam's built-in Proton handles Windows games. PortProton adds a GUI wrapper that doesn't actually improve anything - it's training wheels for people afraid of Steam settings.

For Complex Cases: Lutris

If you need maximum control over Wine/Proton versions, use Lutris:

yay -S lutris

Features:

• GUI for managing Wine versions
• Per-game Wine/Proton selection
• Built-in MangoHud support (FPS overlay)
• GPU selection dropdown
• Full manual control when you need it

But start with Steam. Only reach for Lutris when Steam Proton doesn't work for a specific game.

Configuration: The Portable Setup

Remember from Part 2: your entire Linux personality lives in ~/.config/.

On Arch, this becomes even more powerful:

# Backup your entire setup
tar -czf my-arch-setup.tar.gz ~/.config ~/.local ~/Documents

# New machine, new install
# After creating the same username:
tar -xzf my-arch-setup.tar.gz -C ~/

Everything returns:

• All application settings
• Custom keybindings
• Menu customizations
• Themes and appearances
• Even your application menu entries from ~/.local/share/applications/

On Ubuntu, this works mostly. On Arch, it works perfectly because package versions are current and consistent.

The Transition Plan

If you're convinced, here's how to switch without losing your mind:

Phase 1: Preparation (While still on Ubuntu)

1. Document your installed programs: dpkg --get-selections > my-programs.txt
2. Backup /home/ entirely
3. Note any weird customizations you made
4. Download EndeavourOS ISO

Phase 2: Installation

1. Boot from USB
2. Choose "Online install" (gets latest packages)
3. Select KDE Plasma as desktop
4. Let it auto-detect drivers
5. 20 minutes later, you're done

Phase 3: Setup

1. Copy back your ~/.config/ and ~/.local/ folders
2. Install your programs via pacman and yay
3. Most of your settings are already restored

Phase 4: Learning

• Keep the Arch Wiki open
• Ask AI when stuck
• Join the EndeavourOS forums (helpful community)

Common Objections Addressed

"But I already spent time learning Ubuntu!"

You learned Linux fundamentals - file system hierarchy, package management concepts, configuration patterns. That knowledge fully transfers. You're just switching the implementation details (apt → pacman, PPAs → AUR).

"Arch seems harder."

Arch seems harder because it doesn't hide things from you. Ubuntu creates the illusion of simplicity by abstracting problems away - until they break, and then you're lost.

With Arch, you understand what's happening. That feels harder initially, but it's honest difficulty that makes you competent.

"What if I break something?"

You already broke things on Ubuntu (the Wine library incident). The difference on Arch is:

• The wiki explains why it broke
• The fix is clearer
• The community has documented it
• You learn the actual system, not Ubuntu-specific workarounds

The Bigger Picture

You're documenting your Linux learning journey in real-time, showing beginner struggles. This is valuable content - the Russian Linux community needs more honest, unglamorified guides.

Switching to Arch would:

• Eliminate entire categories of problems you're hitting
• Show viewers the difference between "beginner distro" and "actually functional distro"
• Give you material for better tutorial content (Arch wiki → translate to Russian)

But more importantly: You'll stop fighting the system and start understanding it.

The Pluralism Zoo

Linux is a zoo of technologies and philosophies. Different package formats (deb, rpm, pkg), different init systems (systemd, OpenRC), different display servers (X11, Wayland), different approaches to everything.

This is not a bug. This is the feature.

It means:

• No single point of failure (if Ubuntu dies, Debian continues)
• Innovation happens at all levels
• You can choose based on your actual needs
• The best ideas survive through competition

But as a beginner, this feels overwhelming. That's why you pick one path and master it. You picked Ubuntu. I'm suggesting you pivot to Arch while your fundamentals are still fresh.

Making the Choice

Stay on Ubuntu if:

• You're deeply invested in Snap-based workflows
• You need enterprise LTS support
• Change feels too risky right now

Switch to Arch (EndeavourOS) if:

• You're tired of repository and key management
• You want bleeding-edge packages
• You value learning over hand-holding
• The Arch Wiki appeals to your learning style

There's no wrong choice. But there is an informed choice.

Final Thoughts

Your instinct to ask "why does this work this way?" is correct. Ubuntu's complexity isn't deep complexity - it's accumulated cruft from trying to be both Debian and its own thing.

Arch's complexity is honest complexity. The system is what it appears to be. The wiki tells you the truth. The community expects you to think.

You're already thinking. You're already learning. You're already past the point where Ubuntu's "protections" help you.

The question isn't whether you can handle Arch. You already can.

The question is: do you want to keep fighting Ubuntu's architectural decisions, or do you want to use a system designed for people who actually care how things work?

You're making video guides. You're documenting everything. You're not running away from the terminal. You're exactly the person Arch is designed for.

Welcome to the deep end. The water's fine.

---

Next up: Part 4 could cover customization, themes, and making Linux truly yours - or a Wine/Proton deep-dive for running Windows software. Let me know what's more interesting.