A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
32-bit apps use a sub-set of the same instructions that still exist on current 64-bit systems. Running 64-bit alone does nothing to eliminate any flaws, real or imagined, from the 32-bit side of things.
As @jarfil@jarfil@beehaw.org has stated, 32 bit repos are being de-listed because no one can be bothered to maintain them(on a professional, full-time basis), and that lack of code/functional review could allow flaws to slip through. Meanwhile, a lot of those same 32-bit repos continue to exist(as community-maintained versions - my preferrence anyways) and can be accessed by interested users from most distros. They aren’t blocked, just de-listed and unsupported by those distro maintainers.
Thanks for the explanation! I didn’t realize it was mostly a maintenance limitation, I thought maybe 32-bit instructions could be an extra attack vector on a physical CPU instruction level or something like that.