Fedora 44 and the 32-bit support debate: controversy, repercussions, and uncertain future

  • Fedora proposed removing support for 32-bit software in version 44, but the community showed widespread and rapid pushback.
  • The measure would particularly affect games and derivative distros like the gaming-focused Bazzite, which rely on 32-bit libraries and Steam compatibility.
  • The Fedora team has withdrawn the proposal after strong criticism, but the technical reasons for moving away from 32-bit will remain in place in the medium term.
  • The debate highlights the tension between innovation and compatibility with legacy software and hardware within the Linux ecosystem.

Fedora 44 and 32 bits

During the last weeks, Fedora and its possible removal of 32-bit software support in release 44 have been the subject of one of the most intense debates in the Linux community.The announcement of the proposal sparked widespread protests among users, developers, and project leaders, clearly demonstrating the sensitivity many feel about moving away from compatibility with technologies considered obsolete.

This type of support, especially relevant for those using applications and games that depend on 32-bit libraries, seemed to be hanging in the balance. However, the community mobilized quickly and forced Fedora developers to rethink their plans, at least for now.

The origin of the proposal for Fedora 44 and the technical reasons

The idea of ​​suppressing the 32-bit (i686) libraries and packages In Fedora, it didn't just emerge. For several releases, various distributions have opted to focus exclusively on 64-bit architectures, simplifying maintenance and optimizing resources.

In the case of Fedora, Support for 32-bit bootable images was removed in version 31 (2019)However, running 32-bit software is still supported by the inclusion of specific libraries, which is vital for tools like Steam, OBS Studio, and many classic games.

The proposal presented for Fedora 44 contemplated a two-stage process: first, removing the 32-bit libraries from the standard repositories for the x86_64 architecture, and then permanently stopping compiling those packages. The main reasons were the increasing maintenance effort, the shortage of new developments requiring 32-bit and the need to free up resources to accelerate development and security on 64-bit systems.

Impact on gaming and derivative distros

One of the most controversial aspects of the proposal was the direct impact on gaming platforms like Steam and projects like Bazzitea whirlpool bath, Fedora-derived distribution geared towards gamingBazzite's founder even warned that removing the 32-bit packages would jeopardize the project's continued existence and affect a segment of users who still rely on compatibility with older software.

In the gaming world, many older applications and titles require 32-bit libraries, even on modern 64-bit systems. Steam itself, a fundamental piece of gaming on Linux, still uses 32-bit code and dependencies.. As a result, the idea of ​​removing such support generated a wave of criticism not only from projects like Bazzite, but also among the broader community of players and developers.

Suggested alternatives and technical limits

Among the possible solutions to mitigate the impact, the use of Flatpak and container technologies was mentioned as a method to continue running legacy applications. For example, Wine could make use of your WoW64 configuration to run 32-bit programs on systems that already only include 64-bit binaries. However, these alternatives still have limitations and don't always guarantee full compatibility or the expected performance, especially in the gaming sector.

The arguments in favor of abandoning 32-bit support are not new. Fabio Valentini, one of the authors of the proposal and a member of the Fedora team, emphasized that The global trend is that fewer and fewer projects maintain their 32-bit versions., which complicates management and requires increasing efforts to maintain compatibility.

Community reaction and withdrawal of the proposal

The impact of the proposal was immediate. In forums, social networks, and specialized media, The voices against far outnumbered those in favorUsers and developers of other Fedora-based distributions have expressed concern that their workflows, games, or essential tools could suddenly stop working.

La The developers' response was to take note of the widespread rejectionValentini officially announced the withdrawal of the proposal and acknowledged that the planned timeline was premature. The Fedora team itself admitted that, while the technical decision makes sense in the long term, the ecosystem and users need more time to adapt.

Future prospects and tensions in the evolution towards Fedora 44

Although 32-bit support will continue to be present in Fedora, the debate has highlighted the tension between moving forward and innovating and the need to maintain compatibility with older technologies and applicationsThe development team and package managers themselves have insisted that, sooner or later, the removal of support will be inevitable.

For now, users of Fedora and derivative distributions like Bazzite have a grace period to prepare for a change that, by all indications, has only been postponed. It is recommended that both developers and end users Stay tuned for next steps and adapt your environments and applications to mitigate future impacts.

The controversy surrounding Fedora 44 and 32-bit versions demonstrates that the balance between technological evolution and the needs of the user base is a central issue in the free software world. The community can breathe easy, as critical applications and games that rely on 32-bit libraries will continue to work, at least until the debate is reopened in future releases.

Fedora 42 KDE Edition
Related article:
They are considering removing X11 packages from the GNOME version of Fedora 43 and relying solely on Wayland.