Video Summary
The author acknowledges that gaming on Linux owes a great deal to Valve, particularly due to the release of Proton in 2018. After abandoning Windows on a physical machine in 2017, he was forced to give up games exclusive to that system until Proton arrived via Steam Play, solidifying his decision to use Linux and greatly improving compatibility, especially for single-player users. Initially also available for Mac, Valve focused its development exclusively on Linux to optimize performance on this platform.

Since then, the ecosystem has evolved significantly thanks to community efforts. Native Wayland support improved first in GNOME and then in KDE, allowing applications like RetroArch to run without relying on XWayland. Meanwhile, tools like Heroic Games Launcher have matured, incorporating GOG support, greater reliability, and native Wayland configuration through Wine patches and Proton forks (such as GloriousEggroll, Proton-ME, and the CachyOS version). This has allowed users to choose platforms alternative to Steam, with Heroic standing out as a technically superior option for Wayland compatibility and ease of use, as it preconfigures games without requiring manual parameters.

However, the author criticizes a segment of the community that remains stuck in 2018, ignoring these advancements. This attitude creates two problems: first, the disregard for Valve's vendor locks, such as Steam Input, which does not officially work outside the Steam client, forces manual controller configuration, and lacks stable Wayland compatibility. Second, the willingness to hand over Linux gaming to a corporate monopoly makes the platform appear less neutral than Windows. The author argues that the ecosystem should belong to the community, pointing out the inconsistency of those who invoke freedom of choice while supporting exclusive dependence on a single company.

Finally, he responds to accusations of being anti-Linux or pro-Windows by arguing that SteamOS will not succeed as long as Valve positions it as a secondary or "protest" system against Windows 11. The cancellation of the Steam Machine 2 revealed that it is simply a replicable x86 PC that can be improved with better hardware and alternative distributions, which damaged the image of both the project and SteamOS. The author concludes by dismissing Valve's strategy, predicting that Windows will maintain its hegemony, and criticizing the victim complex of certain community segments, reaffirming that the future of gaming on Linux depends on diversity and genuine user choice.

Video Summary
Microsoft/Xbox is carrying out one of the largest deliberate purges in the history of the industry following the acquisition of major conglomerates like Bethesda and Activision Blizzard. This strategy has led to the closure or threat of closure of multiple studios, such as Ninja Theory, Tango Gameworks, and Arkane Austin, alongside recent mass layoffs at ID Software. The community is pressuring the corporation to return independence and intellectual property to the studios it no longer finds interesting, allowing them to survive in a market that is already experiencing a sharp drop in demand.

The author interprets these actions as a "scorched earth" strategy typical of a monopolistic corporation. The goal would be to weaken or eliminate its main competitors (PlayStation, Nintendo, and Valve) through the partial destruction of the sector, betting on a war of attrition where the survivor takes total control. Although this tactic harms Microsoft in the short term and its reputation is at historic lows, the author has decided to boycott Xbox, adding it to their blacklist alongside Ubisoft, EA, and Epic Games, to avoid funding what they consider a massacre that will severely harm workers and consumers, with the risk that dozens of franchises will be abandoned.

A critical point of this strategy is the recent stagnation of Game Pass, but the most tragic impact could be the potential closure of ID Software, the only AAA studio that develops exclusively using the open Vulkan API (created and driven by the Kronos Group). The author highlights that Vulkan proves to be significantly more efficient and performant than DirectX 12. Despite its promise to operate at a lower level, DirectX 12 typically offers mediocre performance and consumes much more VRAM in practice, making it more viable in many cases to stick with DirectX 11 or use translation layers like DXVK to take advantage of Vulkan's superior capabilities.

Although Vulkan represented the hope of freeing the industry from Microsoft's technological dominance, developers have preferred to stick with DirectX out of familiarity, thereby consolidating Microsoft's API monopoly on PC. In conclusion, the studio massacre not only results in mass layoffs and project cancellations, but also represents a devastating blow to open technologies in video games, once again reinforcing Microsoft's monopolistic control over the sector.

Video summary
A decade and a half ago, Ubuntu established itself as the primary reference for the Linux desktop, standing out more for its user experience than for technological innovations. However, its trajectory began to decline with the push for Mir, a graphical protocol alternative to Wayland. This initiative was met with rejection from manufacturers like Intel and AMD, received limited support from Nvidia, and caused significant discontent within the community. The opposition led by Red Hat ultimately curtailed Mir's reach, marking Canonical's first major technological setback.

Following this failure, Canonical adopted an increasingly conservative policy, showing reluctance to integrate technologies that were already being established in other Linux families. A clear example is the implementation of PipeWire, which arrived in Debian Stable before Ubuntu LTS. This reversed the historical dynamic: whereas Debian was once considered technologically behind Ubuntu, it is now common for Debian to adopt new features before Canonical's distribution. This trend has progressively weakened Ubuntu's influence in the desktop ecosystem.

This loss of relevance became especially evident in the Linux gaming sector, where Ubuntu was dominant a few years ago. Its resistance to adopting more modern standards pushed many users toward Arch Linux and Fedora-based distributions. Furthermore, the stability of bleeding-edge software has improved notably over the last decade, and system recovery mechanisms have become more accessible, reducing the need to rely exclusively on LTS versions.

Canonical's recent policies regarding artificial intelligence and the Snap format have generated further backlash. The community prefers AI to function as a tool at the user's service, rather than as a system component with decision-making capabilities. Likewise, Snap is increasingly perceived as an Ubuntu-exclusive technology. As a result, several derivative distributions are migrating to Debian to have a more standard base free from impositions. A notable case is Tuxedo OS, which will switch its base to Debian Testing, abandon XFS for Btrfs with Snapper to facilitate system recovery, and seek better support for Qt and KDE Plasma.

While the Debian, Red Hat, Arch, and SUSE families converge on shared standards like systemd, Ubuntu has become technologically isolated, introducing particularities that make life harder for its derivatives. This isolation will be exacerbated if major distributions like Linux Mint permanently abandon their Ubuntu-based branch to focus on Debian. Canonical's strategy, including the attempt to package Steam as a Snap (which fragmented usage metrics), has contributed to new projects preferring Fedora or Arch as a base. In summary, Ubuntu has gone from being the central pillar of the Linux desktop to becoming an increasingly marginalized and isolated option within the GNU/Linux ecosystem.

Video Summary
The debate between Flatpak and traditional packaging in Linux has a clear winner: Flatpak. Despite this, this format presents objective disadvantages, primarily in RAM consumption and disk space usage. The high RAM usage is due to the runtimes that applications require. Since different projects and repositories use their own runtimes (such as those from KDE, GNOME, or Freedesktop), library duplication occurs, which multiplies memory consumption when several applications are run simultaneously. Regarding storage, although Flatpak is less efficient than traditional packaging due to not sharing libraries, this disadvantage is often exaggerated. In practice, dozens of applications in this format can take up less than 20 GB, a space that often turns out to be insignificant compared to the current footprint of AAA video games, which exceed 100 GB each. Therefore, the need to expand storage usually stems more from gaming needs than from intensive Flatpak usage.

The real reason Flatpak has surpassed traditional packaging is not an absolute technological advantage, but rather a superior support and maintenance model. On platforms like Flathub, applications are published and verified directly by their original developers. This greatly speeds up bug resolution and ensures constant updates, as bug reports go directly to the project maintainers. In contrast, with traditional packaging, users must rely on third parties to repackage and fix bugs, which often slows down patches or leaves them pending throughout the distribution's lifecycle.

In short, the growing adoption of Flatpak is due to the fact that it offers a more reliable ecosystem with a direct connection to the software creators. Despite its drawbacks in terms of resource usage, the guarantee of receiving official support, immediate updates, and more efficient bug management makes this experience superior for the end user.

Video Summary
The video features gameplay of Elex, a Western-style RPG developed by Piranha Bytes, a German studio known for the Gothic series and other role-playing titles with similar mechanics. The creator explains that his decision to try the game was due to its unconventional nature, as he usually looks for non-traditional experiences in the medium.

The specifications of the system used for the session are detailed: Asus TUF Gaming B660 Plus Wi-Fi D4 motherboard, 32 GB of DDR4 RAM at 3200 MHz, Intel Core i5-12600K processor, 8 GB AMD Radeon RX 7600 graphics card, and a 2 TB Kingston SSD. The operating system is OpenSUSE Tumbleweed with Linux kernel 7.0.12 and KDE Plasma 950.1.2 desktop environment. Regarding graphics settings, interpolation is kept at 90%, anti-aliasing is disabled, anisotropic filtering is set to 8X, and shadow and texture quality are set to ultra, although the rendering distance is slightly reduced. The author notes that he may adjust these parameters as the playthrough progresses to ensure stable performance.

After selecting normal difficulty, the narrative introduction plays. Magaland, a prosperous civilization, is devastated by the fall of a comet that freezes the planet and wipes out its cities. From the ruins emerge new factions with opposing visions: the Berserkers, who use magic to restore the world; the Clerics, interested in recovering ancient technology; and the Outlaws, who seek freedom and survival. The comet also brings Elex, an unknown element capable of enhancing machinery, altering biological evolution, and granting special abilities. Uncontrolled consumption of it creates mutants, while those who manage to master it become the Albes, an addicted and powerful faction that threatens the world's balance. The protagonist, Jack, an Alb commander chosen to change Magaland's fate, is sent on a solo mission after his faction's downfall.

During the first few hours, the combat system is explored, which proves agile but requires constant management of the stamina bar to execute dodges, attacks, and combos. The controls are criticized for their learning curve, although the initial encounters work properly. Character progression requires visiting specific instructors to assign attribute points and unlock skills, avoiding a free-form creation system Fallout-style. The game lacks auto-save and features a slow pace, focused on exploration, looting, and survival.

The open world is characterized by a polished aesthetic that compensates for the use of an older-generation graphics engine. Dynamic weather, such as constant rain, and the feeling of a living environment contribute to an immersive and relaxing experience. The author favorably compares the atmosphere to that of Fallout: New Vegas, highlighting the freedom to get lost on the map, interact with NPCs, and make moral or faction-based decisions. However, he warns that the difficulty can scale quickly, especially in encounters with multiple enemies or hostile creatures.

Throughout the journey, the protagonist meets various key characters. Duras, a Berserker warrior, guides him to Goliath, where he meets Ragnar, the faction leader, and explores options to earn his place through quests or trading. Later, he crosses paths with Ray, an outlaw seeking revenge for a bounty placed on his head signed by a mysterious "W," possibly Wyatt. He also interacts with William, Duke Logan's uncle, who runs the settlement of Tavar and asks for help resolving internal conflicts among his subordinates. These interactions reveal the political tensions, resource scarcity, and mutual distrust among the factions.

During the playthrough, performance fluctuations are observed, with high CPU usage suggesting optimization that depends heavily on this component. The author adjusts some graphical options to maintain stability but keeps the overall settings high. After approximately three and a half hours of gameplay, he concludes that Elex offers a solid, atmospheric, and addictive experience, with a classic RPG approach that prioritizes exploration, fragmented storytelling, and decision-making. Despite its technical limitations and controls that could use improvement, the title manages to capture his attention and promises a long playthrough.

Video Summary
The launch of the Steam Machine 2 has highlighted a strategic mistake by Valve: marketing the product while sacrificing its main advantage, the price-to-performance ratio. This decision has made acquiring the device pointless for most users and has debunked the mistaken perception that it is a traditional console. In reality, it is a standard x86 PC whose specs can be easily replicated or even surpassed with a custom-built machine, eliminating any justification for purchase except for die-hard brand followers.

As a viable alternative, it is shown that it is possible to build a PC with a similar foundation (a mid-to-high-end processor and 24 to 32 GB of RAM) and invest the remaining money in a significantly better graphics card, such as an RX 9070 XT, for less than the price of the most basic Steam Machine 2 model. By installing a third-party Linux distribution similar to SteamOS, like Bazzite, you get an equivalent or even improved experience without needing to buy the official hardware, taking advantage of the fact that the components and base software are standard and widely available.

This commercial misstep has exposed the structural weaknesses of SteamOS as a platform. By fundamentally relying on the Win32 API, the operating system offers no real advantages over Windows 11; any perceived benefit is due more to Windows' flaws than to SteamOS' own merits. The platform lacks a differentiating value compared to other Linux distributions, and its viability depended on maintaining an illusion of a monolithic product, which has now faded after it was revealed that it uses generic components and open software stacks, which would even allow installing Windows without much trouble.

To ensure the long-term survival of the platform, Valve must abandon its current approach and give SteamOS its own value through Linux-exclusive content. Releasing flagship titles, such as Half-Life 3, exclusively on this platform would be the most logical way to incentivize the purchase of dedicated hardware; publishing them simultaneously on Windows nullifies any reason to buy a Steam Machine. If the company does not correct its course and continues to rely on an operating system without its own identity, it risks SteamOS being discontinued, especially if Microsoft improves Windows. The success of future devices will depend on a much more ambitious technological strategy that goes beyond mere price-to-performance ratios.

Video Summary
The video presents gameplay of Soldiers, an indie-developed 2D Metroidvania that stands out for its difficulty and hardcore style, aimed at players looking for a challenge rather than a straightforward experience. The creator details the technical setup used: a PC with an Asus TUF Gaming B660 Wi-Fi D4 motherboard, Intel Core i5-12600K processor, 32 GB of DDR4 RAM, an 8 GB AMD Radeon RX 7600 graphics card, and 2 TB of SSD storage. The operating system is OpenSUSE Tumbleweed on x86_64 architecture, and the game runs through the Heroic Games Launcher via its official Flatpak version, using a recent build of Proton-GE to ensure Linux compatibility.

Technically, the title runs natively on Wine/Proton with moderate CPU and GPU usage, though it does not reach 90 frames per second despite its retro aesthetic inspired by 8-bit and 16-bit consoles. The game lacks modern features such as Ray Tracing or DLSS, prioritizing a classic experience. Although Soldiers received negative reviews at launch for being unpolished, its developers have kept it actively maintained with constant updates that have considerably improved its current state and resolved numerous initial issues.

Regarding gameplay, the protagonist selects the knight class, focusing on physical combat rather than magic. The design blends Metroidvania-style exploration with classic The Legend of Zelda mechanics, such as using bombs to break walls, collecting tear fragments to increase maximum health, and items like the valkyrie feather, which functions as an automatic reviver similar to Zelda's fairies. The world is primarily set in dark, spider-infested caves, where the player faces enemies that respawn if progress is not saved, and must manage resources to forge armor or boost stats using minerals like roquirite and ragnarite.

The creator notes that controls feel more precise with the controller's D-pad rather than the analog stick, as the latter makes dodging and climbing stairs more cumbersome. Throughout the playthrough, the video showcases boss battles against foes like Llanza Oscura, the acquisition of new abilities (such as a sword flurry), and the search for esmeracnid gems that must be placed in a specific pattern to unlock a main gate. Despite the predominantly underground settings and familiar formula, the game remains entertaining due to its old-school approach and well-balanced difficulty.

Finally, Soldiers is recommended to fans of challenging 2D Metroidvanias and those who appreciate indie titles with a classic soul. The creator mentions that he is balancing this playthrough with other games like Turok 2: Dinosaur Hunter, and wraps up the video by inviting viewers to follow his upcoming content, deliberately avoiding digressions about future purchases or tangential comparisons to focus exclusively on the experience showcased.

Video Summary
The video features gameplay of Night Dive Studios' remaster of Turok 2: Six of Evil. The narrator expresses his disappointment because this version is based on the 1999 PC port, which already softened the difficulty by allowing quick saves, rather than preserving the more demanding essence of the original Nintendo 64 version, where reaching specific save points was mandatory to save progress. He considers that the remaster "casualizes" a formula that had already lost part of its original challenge, unlike what happened with the first title in the saga, whose remaster was indeed based on the console version.

To run the game, a system with an ASUS TUF Gaming B660 Plus Wi-Fi D4 motherboard, Intel Core i5-12600K processor, 32 GB of DDR4 RAM, and an AMD Radeon RX 7600 graphics card is used, complemented by a 2 TB Kingston SSD. The operating system is Linux with a Wayland environment and Mesa drivers, running the Windows version of the game through Proton via the Heroic Games Launcher. The graphical settings use the Vulkan API, 1440p resolution, and SMAA anti-aliasing, achieving a stable performance of approximately 165 FPS, which allows for smooth operation without overloading the GPU.

During the gameplay, it is highlighted that the Nintendo 64 versions aged better than other titles on the console thanks to their analog stick aiming system, which simulates the function of a second joystick. The remaster introduces changes such as the ability to travel between portals to replenish health and ammo, something not present in the originals. Although the narrator criticizes the limited lives system as obsolete in the face of free saving, he acknowledges that the "hard" difficulty level and enemy respawns maintain an acceptable challenge. Technical details are also mentioned, such as the dense fog from the original engine used to hide the draw distance, and the contextual death and damage animations that have stood the test of time.

The game sets the mission of finding five sacred talismans and eliminating cursed dates to progress, paving the way for the third installment. Reference is made to the legacy of Iguana Entertainment, the original developer, whose team was later hired by Nintendo to found Retro Studios and create Metroid Prime, taking the level design and exploration of the N64 version of Turok 2 as a base. The narrator compares the experience to other console shooters ported to PC, pointing out that they lose their challenge when played with a keyboard and mouse, and defends the use of a controller as the natural environment for this type of title.

The gameplay experience focuses on map exploration, resource management through respawn points, and battles against hordes of enemies that act as bullet "sponges." The narrator takes advantage of mechanics like supply respawns to replenish before advancing, criticizes the basic artificial intelligence of some enemies, and highlights the quality of the soundtrack. Despite his reservations about the remaster's design decisions, he ends by acknowledging that the game exceeds his initial expectations and maintains solid gameplay, culminating with the introduction of final objectives such as destroying soul doors and defeating the Sisters of Despair.

Video Summary
Migrating from Windows 11 or an Intel-based Mac to GNU/Linux is a sensible decision to avoid planned obsolescence, eliminate telemetry and bloatware, and ensure security updates. However, the migration often fails when the user tries to adapt to the new operating system all at once, which creates an overwhelming learning curve and leads to a return to Windows or macOS. To avoid this scenario, a gradual and structured approach is recommended.

The first step is to perform a complete backup of important data. Next, download the ISO of the chosen distribution (such as Bazzite) and run a live session exclusively to verify the detection of critical hardware (Wi-Fi, Bluetooth, Ethernet), without paying attention to performance, as live sessions tend to be slow. Once basic compatibility is confirmed, the user must radically replace all applications on their current system that lack a native Linux version with compatible equivalents. For example, Thunderbird instead of Outlook, LibreOffice or OnlyOffice instead of Microsoft Office, and Firefox as the primary browser. This replacement should be complete, without leaving old programs installed out of inertia, since users tend to focus their experience on the applications rather than the operating system itself, which greatly eases the transition.

After adapting to the new workflow with the alternative applications, it is advisable to practice with the Linux distribution in a virtual machine (VirtualBox or VMware) to familiarize yourself with its fundamentals. When the user feels comfortable, they should make a radical switch to the operating system, completely removing Windows or macOS. Dual booting is strongly discouraged, as inertia often leads to the gradual abandonment of Linux. The only acceptable exception is keeping the old system exclusively for very specific tasks with no Linux alternative, such as online games with incompatible anti-cheat software or professional software like Photoshop, rebooting immediately back into Linux once the task is finished.

Regarding technical aspects, although the user experience on Linux has improved significantly, hardware support still relies more on the community than on manufacturers. It is recommended to avoid NVIDIA cards unless they are required for specific professional work or AI, as AMD/Radeon drivers offer better integration, especially with Wayland, and require less maintenance. Finally, instead of LTS distributions like Ubuntu or Linux Mint, bleeding-edge options like CachyOS or Bazzite are preferred, as they provide kernels and drivers updated directly by the distro developers, without relying on unverified external repositories, which is ideal for gaming and modern hardware. Valve's contribution to the ecosystem, for example, has focused more on RADV, AMDGPU, and Proton than on graphical interfaces, reinforcing the current maturity of the Linux environment for everyday use.

Video Summary
Firefox has officially integrated support for hardware-accelerated video playback via Vulkan, a more modern API than the current OpenGL, which has been used by the browser until now. Although Vulkan was announced in 2016 and has already seen a decade of development, its adoption in the gaming sector faces competition from Microsoft's DirectX 12. The implementation in Firefox relies on VAAPI for hardware acceleration, which poses a challenge with NVIDIA's official drivers, as they do not include native support for that API. To work around this, users must rely on a community-driven reimplementation that acts as a wrapper around NVENC, enabling hardware acceleration to function without it being an officially supported feature by the manufacturer.

One of the main drivers behind this feature is Martin Stransky, a Red Hat employee and key developer for Firefox's hardware acceleration, native Wayland support, and the verification of its Flatpak packages. Thanks to contributions like his and the backing of Red Hat, Linux remains the only operating system where Firefox maintains genuine technological competitiveness against Chromium, offering more mature Wayland and hardware acceleration implementations than its main rival.

Regarding technical advantages, the transition to Vulkan should theoretically improve performance, although the most significant gain is expected in power efficiency. By operating at a lower level and communicating more directly with the hardware, Vulkan could reduce power consumption, which would translate into longer battery life for laptops and mobile devices. However, given that modern GPUs already possess substantial power, this improvement is not considered revolutionary in terms of raw performance.

On the other hand, the removal of OpenGL support is not planned for the short or medium term, at least not for the next ten years, due to the large base of older hardware that lacks Vulkan compatibility. This limitation is explained by the API's origins: Vulkan is an evolution of Mantle, a technology created by AMD and donated to the Khronos Group. This legacy gives Radeon cards a historical advantage in multi-generational compatibility. In contrast, Intel solidified its support around the eighth-generation processors, while NVIDIA offers a robust implementation primarily from the Turing architecture onward, with decreasing compatibility in earlier generations. For all these reasons, the coexistence of both APIs will be maintained for a long time to ensure compatibility with the entire available hardware ecosystem.

Video Summary
Epic Games has announced Unreal Engine 6, whose initial version will debut in Rocket League. The author uses this news to harshly criticize the company and its CEO, Tim Sweeney, accusing him of hypocrisy. Unlike business figures who openly acknowledge their commercial nature without pretense, Sweeney presents himself as a defender of consumer freedom, which the narrator considers false based on his own experience: the removal of the native Linux and Mac versions of Rocket League on Steam and the initial refusal to refund his money.

Regarding the graphics engine, the text notes that Unreal Engine 5 has proven problematic due to its high hardware requirements and poor optimization, particularly when implementing technologies like Lumen or Nanite. The author emphasizes that the reality of PC gaming is far from the myth of "NASA-grade" computers: the most popular graphics card remains the RTX 3060, and most users play at 1080p. In light of this, he predicts that Unreal Engine 6 will attempt to fix its predecessor's shortcomings by turning to artificial intelligence, a technology he considers overhyped and which could worsen the situation rather than resolve it.

As a counterpoint, the narrator praises The Legend of Zelda: Majora's Mask (N64), highlighting its artistic attention to detail, its living and interactive world, and its balanced scope compared to today's empty open worlds. He particularly admires its technical optimization, achieved with a 94 MHz processor, 8 MB of RAM, and a 256-megabit cartridge. He contrasts this with modern UE5 games, which, despite their visual realism, often offer inert and less interactive environments than older titles like Deus Ex or Majora's Mask, and whose graphical quality does not surpass well-optimized works like Batman: Arkham Knight or the Resident Evil 3 remake.

The analysis expands into a structural critique of the industry: excessive reliance on hardware power has replaced optimization, a trend fueled by technologies like DLSS and frame generation, which serve as excuses for not polishing the software. The author attributes this dynamic to the Western capitalist model, which is based on infinite economic growth that demands increasingly expensive and grandiose productions, ignoring the actual limits of demand. In contrast, he highlights the pragmatic approach of East Asia (exemplified by Capcom and Nintendo), which prioritizes cost control, the intelligent reuse of resources, and design quality, allowing them to stand out in a saturated market.

Finally, the text concludes that Japan and other Asian countries have chosen to prioritize their social and cultural standards over unlimited economic expansion, a decision that allows them to maintain their identity in the face of Western cultural decay. As for the future of video games, the author anticipates that Unreal Engine 6 will continue the current trend of technological bloat and poor optimization, dragged along by the artificial intelligence bubble and the logic of infinite growth. He considers that the Western industry is in the process of imploding due to its refusal to adapt to the reality of the market and available hardware.

Resumen del video Hace tiempo anuncié que no compraría más tarjetas gráficas dedicadas, pero recientemente reconsideré esa decisión. Mi equipo, centrado en un procesador i5-12600K de casi cuatro años y medio, ha mantenido un rendimiento sólido para mis tareas cotidianas, especialmente tras actualizar el firmware de la placa base y utilizar OpenSUSE Tumbleweed, que ofrece mayor fluidez que otras distribuciones como Fedora. Aunque los videojuegos modernos suelen presentar una optimización deficiente, no constituyen mi prioridad actual, por lo que el sistema sigue siendo más que suficiente para mis necesidades generales. El cambio más significativo en mi flujo de trabajo fue la actualización a un monitor de 1440p a 165 Hz. Grabar a esta resolución con OBS Studio sobrecargaba al procesador, provocando una pérdida considerable de fotogramas y afectando la calidad final. Sin embargo, la RX 7600 de 8 GB ha sido determinante al permitir la codificación AV1 directamente por GPU, lo que solucionó el problema de rendimiento. Además, este formato ofrece una mayor calidad de imagen a igual bitrate en comparación con x264, H.264 o H.265, optimizando considerablemente mis grabaciones. Dado que la codificación por GPU es crítica para mí y el lanzamiento estable de AV2 se acerca, he decidido posponer la compra de una nueva gráfica hasta que AMD o Intel incorporen soporte nativo para este formato. Espero que la serie mínima compatible sea similar a la actual (RX 7000/9000 o equivalentes de Intel con 16 GB de VRAM). Actualmente, comparo los codificadores AV1 disponibles: AOM ofrece un mejor soporte de perfiles de color, pero es más lento y carece de multiprocesamiento; por el contrario, SVT-AV1 es mucho más rápido gracias a su optimización multicore, aunque con un manejo de color más limitado. Para creadores caseros como yo, la velocidad de renderizado suele ser prioritaria sobre la gestión avanzada del color. Mi proceso actual consiste en capturar gameplay directamente con la GPU en AV1 y luego reconvertir el archivo en Kdenlive usando SVT-AV1 por CPU para reducir su tamaño antes de subirlo a YouTube, ya que los archivos crudos generados por la tarjeta gráfica pueden resultar demasiado voluminosos. Esta etapa de renderizado consume casi toda la noche, y con codificación AV1 pura sería aún más lenta. Por todo ello, la inminente llegada de AV2 me sirve como excusa válida para esperar: si logra combinar la eficiencia y calidad de AV1 con una velocidad de renderizado superior, será una mejora decisiva que justificará completamente la inversión en nuevo hardware.

Resumen del video Se presenta la versión 21 de Agama, el instalador basado en tecnología web de OpenSUSE, que ya es estándar en Leap pero sigue siendo una alternativa a YaST en Tumbleweed. Aunque la versión 20 no fue anunciada oficialmente, esta nueva actualización introduce mejoras significativas: avisos más claros sobre la selección del entorno de escritorio, mejor gestión de red mediante interfaz web (ideal para instalaciones remotas), capacidad de instalar sobre configuraciones LVM existentes, configuración explícita de fuentes NTP y restricciones de acceso a red durante la instalación por seguridad. Además, systemd-boot se establece oficialmente como gestor de arranque predeterminado, aunque el autor señala que ya estaba presente en versiones anteriores. El texto critica la estrategia de comunicación y marketing de OpenSUSE, lo que limita el alcance de la distribución frente a otras como CachyOS, a pesar de su gran potencial en entornos de escritorio y gaming. Durante la demostración de instalación de Tumbleweed, se destaca un error conocido en la interfaz: si no se selecciona el idioma correctamente al inicio, la pantalla aparece en inglés. La solución consiste en aceptar la configuración inicial, volver a seleccionar el idioma español y confirmar, lo que traduce toda la interfaz y configura correctamente el sistema. El proceso continúa con la definición del nombre de host, la corrección de la zona horaria (Madrid), la activación del cifrado de disco (recomendado para portátiles) y la selección de patrones de software. Se opta por el escritorio Nemo, se añaden paquetes multimedia y ofimáticos, y se prefiere SELinux sobre AppArmor por su mayor estrictura. Finalmente, se crea un usuario con privilegios elevados mediante sudo, evitando habilitar la cuenta root, y se inicia la instalación preferiblemente por conexión cableada. Una vez finalizada la instalación y tras reiniciar el sistema (que arranca con systemd-boot y solicita la contraseña de cifrado), se procede a una limpieza exhaustiva del entorno. El autor desinstala las aplicaciones preinstaladas en formato RPM, como Totem, Evince y los juegos de Nemo, prefiriendo rellenar el sistema con Flatpaks para mantener un sistema raíz ligero. Asimismo, critica a YaST por requerir obligatoriamente acceso root y lo considera obsoleto. Para sustituirlo, instala mediante zypper el gestor de paquetes gráfico Muon, que funciona correctamente con sudo y ofrece una interfaz similar pero más práctica. También se elimina por completo YaST y sus dependencias, marcándolos para que no vuelvan a instalarse en futuras actualizaciones. Para optimizar el sistema para videojuegos y mejorar la gestión energética, se instalan paquetes adicionales como power-profiles-daemon (para controlar los modos de ahorro y rendimiento), steam-devices, la política de SELinux orientada a gaming (linux-policy-target-gaming) y las librerías de 32 bits necesarias para la compatibilidad con títulos Windows y Linux. La gestión del sistema se delega a Cockpit, que se configura en modo local por seguridad. A través de su interfaz web se administran el cortafuegos, el almacenamiento BTRFS, los snapshots de Snapper (útiles para revertir cambios) y los contenedores Podman. El autor concluye destacando la notable mejora en la velocidad de zypper, el correcto funcionamiento de los snapshots y su preferencia por Cockpit sobre YaST, considerando que Agama y sus herramientas complementarias están madurando positivamente a pesar de seguir en desarrollo.

Resumen del video El autor dejó de utilizar Windows en máquinas físicas a finales de 2017, aunque ya había migrado su trabajo productivo a Linux en 2012. Su transición inicial se vio frenada temporalmente por la incapacidad de LibreOffice Writer para abrir archivos .doc antiguos, un problema que se resolvió al año siguiente. Entre 2012 y 2017, Windows quedó relegado exclusivamente a la ejecución de videojuegos, ya que las alternativas nativas para Linux o soluciones como PlayOnLinux no ofrecían un rendimiento aceptable, especialmente en hardware antiguo. La decisión definitiva de abandonar Windows se consolidó cuando una actualización de Windows 10 dejó el sistema inutilizable tras tres meses, y al planificar su siguiente equipo con procesadores Ryzen, se enfrentó a la falta de compatibilidad oficial de Windows 7. Tras un fallo de hardware en su configuración original (Ryzen 7 1700) derivado de un incidente con un SAI y una actualización de firmware, decidió renovar la máquina de forma conservadora: mantuvo la caja, la fuente de alimentación y 32 GB de RAM DDR4-3200, pero instaló un Intel Core i5-12600K y, en 2023, reemplazó su RX 580 por una RX 7600 XT. Durante casi nueve años, ha observado una mejora constante en la experiencia de usuario de Linux. Actualmente, está tan familiarizado con el entorno Linux y sus distribuciones basadas en systemd que le resulta prácticamente imposible utilizar o incluso instalar Windows en un equipo físico, considerando que los entornos de escritorio de Linux son más sencillos y requieren menos mantenimiento que el sistema de Microsoft. En cuanto a los videojuegos, se ha convertido en un defensor firme de ejecutar compilaciones para Windows mediante Proton en lugar de usar versiones nativas para Linux. Argumenta que la API Win32 ofrece mayor estabilidad frente a los cambios frecuentes de las APIs de Linux, además de proporcionar un mejor rendimiento y una integración más fluida con el sistema operativo, como la correcta detección del idioma o la compatibilidad total con mandos de PlayStation. Asimismo, destaca que Proton facilita la ejecución nativa sobre Wayland sin depender de que cada motor de desarrollo implemente soporte específico, lo que garantiza una experiencia más estable y moderna que forzar la ejecución a través de Xwayland. Su metodología de trabajo en Linux ha evolucionado significativamente con el uso de sistemas operativos inmutables. Para mantener el sistema anfitrión limpio y aislado, ejecuta aplicaciones mediante Flatpak (incluyendo Steam para aislar Proton), gestiona servicios y entornos LAMP a través de Podman para facilitar la creación de múltiples configuraciones según el contexto, y utiliza Distrobox para aislar compiladores, herramientas de monitorización y software específico. Por ejemplo, planea ejecutar Arx Libertatis mediante un contenedor Distrobox basado en Fedora Rawhide, exportando la aplicación al lanzador principal del sistema. Concluye reforzando su compromiso con Linux como único sistema operativo físico y anuncia que publicará un tutorial sobre el uso básico de Distrobox.

Resumen del video Tras unos días personales intensos, el autor decide abordar de forma ligera un tema controvertido: su postura crítica hacia Steam. En un video anterior explicó cómo la plataforma está fragmentando el gaming en Linux, separando su ecosistema oficial del resto y consolidándose como propietaria de facto del sector. El creador se opone firmemente a esta centralización, defendiendo que los videojuegos en Linux deberían ser un proyecto comunitario y no depender exclusivamente de una sola empresa. Otra razón fundamental es la supuesta marginación deliberada de Flatpak por parte de Valve, con el objetivo de impulsar las ventas de sus dispositivos como la Steam Deck y una futura Steam Machine 2. A medida que Valve ha reducido su implicación en el mantenimiento de la versión Flatpak de la aplicación, esta ha experimentado un notable descenso en calidad. Además, el ecosistema se vuelve cada vez más cerrado: ciertos títulos exigen parámetros de lanzamiento que emulan la Steam Deck para ejecutarse mediante Proton, una estrategia que perjudica a los escritorios Linux estándar y favorece exclusivamente al hardware oficial o compatible con SteamOS, como la Legion Go S. A pesar de estas críticas, el autor reconoce la importancia del reempaquetado Flatpak para mantener la compatibilidad con sistemas operativos inmutables y garantizar la seguridad. Este formato aísla Wine y Proton del sistema anfitrión, minimizando los riesgos asociados a la ejecución de malware diseñado para Windows. En conclusión, Steam no ofrece el soporte esperado ni en el formato deseado, especialmente en lo relativo a la ejecución de videojuegos compilados, lo que consolida su postura crítica hacia la plataforma.

Resumen del video Microsoft muestra una notable indecisión respecto al lanzamiento de Windows 12, alternando entre retrasos y priorizar la corrección de Windows 11, un sistema que la propia compañía reconoce estar bastante afectado por actualizaciones que suelen romper más funcionalidades de las que solucionan. Esta situación evidencia la falta de un modelo de actualización estable o rolling release fiable, lo cual contrasta con la consistencia que ofrecen distribuciones Linux modernas como OpenSUSE Tumbleweed o CachyOS. Uno de los principales lastres de Windows es su acumulación de componentes heredados de décadas anteriores, como fragmentos de Windows 95, 98 o incluso 3.1, mantenidos por una política rígida de retrocompatibilidad que el autor considera sobrevalorada. Esta estrategia ha convertido al sistema en una estructura sobrecargada e ineficiente, dado que incluso la compatibilidad con software antiguo no está garantizada y a menudo requiere parches externos o modos de ejecución forzada, lo que desmiente la supuesta infalibilidad de dicha política. Esta carga histórica hace que Windows 11 exija recursos considerables, especialmente memoria RAM, más allá del polémico requisito de TPM 2.0. Aunque es frecuente escuchar recomendaciones para migrar a Linux en equipos con poca capacidad, los entornos Linux preconfigurados tampoco son sistemas ultraoptimizados por defecto; ejecutan numerosos servicios y software adicional para cubrir usos generales, al igual que Windows. La mayoría de los usuarios de Linux en escritorio no son expertos técnicos, tal como demuestra el propio Linus Torvalds, quien fuera de su trabajo en el kernel actúa como un usuario convencional, prefiere interfaces sencillas y critica la complejidad innecesaria de distribuciones como Debian durante su instalación. A diferencia de Windows, la comunidad Linux ha comenzado a retirar periódicamente componentes obsoletos, controladores antiguos o módulos vulnerables del kernel y de Mesa para mantener la sostenibilidad del ecosistema. Aunque esta limpieza ocasional genera molestias en algunos usuarios, es una medida necesaria que evita que el software se convierta en un lastre creciente. Mientras Linux se aligera selectivamente, Windows sigue acumulando código legado sin eliminarlo, lo que podría llevarlo a un colapso funcional a largo plazo. Finalmente, existen rumores sobre el uso intensivo de inteligencia artificial en el desarrollo y mantenimiento de Windows 11, con una supervisión humana aparentemente insuficiente para corregir sus errores. El autor muestra escepticismo hacia las capacidades actuales de la IA, prefiere utilizarla de forma aislada y advierte que su implementación masiva en el desarrollo de software podría agravar los problemas históricos de ineficiencia en el aprovechamiento del hardware, especialmente en un contexto donde muchas empresas sustituyen personal técnico por automatización.

Resumen del video El kernel de Linux enfrenta una situación de seguridad crítica tras el descubrimiento reciente de vulnerabilidades significativas como CopyFail, DirtyFrag y Fragnesia. Según se sugiere en el análisis, este aumento en la detección de fallos podría estar relacionado con el uso de modelos de inteligencia artificial para facilitar su hallazgo. Dado que Linux opera como un kernel monolítico, las vulnerabilidades de escalada de privilegios son especialmente comunes y peligrosas. Para mitigar este riesgo, surge el proyecto Module Jail, una herramienta de endurecimiento diseñada para reducir la superficie de ataque del sistema al deshabilitar componentes innecesarios. Module Jail funciona mediante un script que compara los módulos del kernel actualmente cargados con el árbol completo de módulos disponibles. A partir de esta comparación, genera un archivo de lista negra en la configuración del sistema que impide la carga de módulos no utilizados. La herramienta está concebida como una acción de configuración única y se recomienda ejecutarla únicamente cuando el sistema alcanza su estado estable, con todos los servicios activos, sistemas de archivos montados y controladores esenciales ya cargados, para evitar bloquear funcionalidades críticas. El proyecto ofrece tres perfiles de configuración predeterminados: uno conservador orientado a servidores virtualizados o físicos, otro para equipos de escritorio que preserva controladores de Wi-Fi, Bluetooth, audio y vídeo, y un perfil mínimo que solo mantiene los módulos del sistema de archivos y los estrictamente necesarios. Aunque su diseño inicial parece priorizar entornos de servidor con configuraciones estáticas, se plantea que también podría ser útil en ordenadores de escritorio, dada la naturaleza dinámica de estos sistemas y su tendencia a ejecutar más software del necesario. No obstante, se advierte que una implementación rígida podría bloquear dispositivos de uso intermitente, como mandos de videojuegos USB, por lo que se necesitaría cierta adaptabilidad para este entorno. En cuanto a compatibilidad, Module Jail ha sido probado en Ubuntu 24.04, Debian y Rocky Linux, con pruebas adicionales basadas en contenedores para Arch Linux, Alpine y openSUSE Tumbleweed. Se ofrecen paquetes precompilados para distribuciones basadas en Debian y RPM (Ubuntu, Red Hat, Fedora y Rocky), mientras que los usuarios de openSUSE deberán aplicar la configuración manualmente. La herramienta es fácilmente reversible: basta con eliminar el archivo de lista negra generado y reiniciar el sistema para restaurar el comportamiento original del kernel. El autor concluye recordando casos anteriores donde poner módulos específicos en lista negra mejoró la estabilidad, y espera que Module Jail evolucione para adaptarse mejor a distintos entornos de uso.

Resumen del video El vídeo responde a las dudas surgidas tras un anuncio sobre el cambio a Linux, aclarando que las versiones v1, v2, v3 y v4 de x86-64 no son características del sistema operativo, sino conjuntos de instrucciones implementadas a nivel de silicio por Intel y AMD. Estas versiones se introducen para acelerar operaciones frecuentes mediante hardware, ofreciendo un rendimiento superior al cálculo por software. Para ilustrarlo, se utiliza un ejemplo hipotético donde cada versión añade nuevas instrucciones optimizadas manteniendo la retrocompatibilidad con las anteriores, creando una evolución lineal y acumulativa. La implementación de estas versiones está definida por los fabricantes y suele utilizarse para diferenciar gamas de procesadores más que generaciones. Un chip de gama media reciente podría no soportar v4, mientras que uno de gama alta sí, incluso si pertenecen a la misma generación. Además, un procesador solo se considera compatible con una versión si implementa todas sus instrucciones; de lo contrario, se clasifica en la versión inferior. Esta estrategia comercial puede generar confusión entre los usuarios, aunque su impacto práctico es limitado salvo en hardware muy antiguo. En el ecosistema Linux, la gestión de estas versiones varía según la distribución. OpenSUSE y CachyOS detectan automáticamente el soporte del procesador e instalan paquetes compilados para v3 cuando es posible, recurriendo a v1 en caso contrario. Red Hat Enterprise Linux exige v3, mientras que Arch Linux redujo su requisito base a v2 en su versión 10. Distribuciones empresariales como Rocky Linux mantienen enfoques similares, aunque su relevancia en entornos domésticos ha disminuido debido a la mayor estabilidad del software moderno. En uso doméstico y gaming, las mejoras de rendimiento derivadas de estas instrucciones suelen ser marginales. El autor observa una mayor fluidez en el escritorio con OpenSUSE (compilado para v3) frente a Fedora (v1), pero en videojuegos como Deus Ex: Human Revolution o Fallout: New Vegas, la diferencia entre Proton (v3) y la bifurcación de GloriousEggroll (v1) es mínima, con apenas ligeras variaciones en FPS y estabilidad del frame time. Esto respalda la postura de que compilar para versiones superiores no ofrece ventajas revolucionarias en entornos estándar. La compatibilidad es estrictamente unidireccional: el software compilado para una versión superior no funcionará en procesadores que solo soporten versiones anteriores, lo que explica los fallos de ejecución de aplicaciones modernas en hardware antiguo. En la práctica, el sistema operativo suele gestionar esta selección automáticamente. Solo en instalaciones manuales es necesario conocer el nivel de soporte del CPU para elegir la compilación adecuada. En resumen, aunque las instrucciones a nivel de silicio mejoran teóricamente el rendimiento, su impacto real en tareas cotidianas es limitado y su manejo se simplifica gracias a la gestión automática de paquetes en la mayoría de distribuciones actuales.

Resumen del video Debido a cambios recientes en su entorno, el autor ha actualizado su configuración para jugar en Linux, adoptando OpenSUSE Tumbleweed como sistema operativo. Para gestionar las distintas capas de compatibilidad, utiliza Proton Plus, una herramienta que permite instalar y actualizar automáticamente versiones como CachiOS y ProtonMH. Esta aplicación es compatible tanto con Heroic Games Launcher como con Steam, aunque el autor prefiere la primera. Para la bifurcación Glorious Eggroll, sigue confiando en Heroic Games Launcher, donde la actualización debe realizarse manualmente desde el gestor de Wine, a diferencia de la automatización que ofrece Proton Plus. Como capa de compatibilidad predeterminada, elige Proton CachiOS, activando de forma habitual el soporte nativo para Wayland proporcionado por Wine y el hack de FSR (ajustado por defecto a 5). Estas opciones se desactivan solo en títulos menos exigentes o cuando se utiliza el reescalado nativo del motor Unreal Engine 4. El autor destaca que prefiere ejecutar las versiones para Windows a través de Proton en lugar de las compilaciones nativas para Linux, ya que considera que ofrecen mejor rendimiento y compatibilidad. Además, comenta su experiencia con motores gráficos, señalando que Unity funciona bien en 2D pero le resulta deficiente para juegos 3D, y critica el rendimiento de Unreal Engine 5. Un aspecto crucial para quienes utilicen OpenSUSE Tumbleweed con Flatpak es la instalación de paquetes adicionales que no se incluyen automáticamente como dependencias, a diferencia de lo que ocurre con los repositorios nativos RPM. Es necesario instalar selinux-policy-targeted-gaming para permitir la ejecución de juegos mediante Proton o Wine bajo las políticas de SELinux, y libselinux32 para garantizar la compatibilidad con ejecutables de 32 bits. Si se utiliza Steam en formato Flatpak, también se requiere el paquete steam-devices para la integración correcta de los mandos. Para activar el soporte nativo de Wayland en Steam, es preciso añadir un parámetro de lanzamiento específico en las propiedades de cada juego, un proceso que Heroic Games Launcher simplifica al permitir configurarlo de manera global desde la aplicación. El autor señala que las versiones oficiales de Proton de Valve aún no incluyen soporte nativo para Wayland, ni siquiera en sus ramas experimentales. Con estos ajustes, herramientas y consideraciones sobre Flatpak, se detalla completamente su marco de trabajo actual para el gaming en Linux.