Well, looks like they did it.
Rust, the "secure" language used for firefox and librsvg, no longer work on AthlonXP, Athlon, Pentium III (Katmai and older), Pentium II, and anything older. Because of rust's decision to call "i686" at least a Pentium 4 (with SSE2), these older machines have been left out to pasture. Not sure how hard it is to remove SSE2 instructions from rust's instruction scheduler and still produce a working binary...
I've been depending on these old machines to keep on working as they still share the same instruction set...or seemingly do, until people actually force one to have SSE2.
librsvg is significant as it's a component of gtk+ -- which is used by xfce4 and gnome desktop environments. Looks like KDE or lxde may need to be looked at, and even KDE with its dependency on QT5 and QT5's insistence on having SSE2 instructions, though that can be worked around.
So I guess the original P4, Pentium-M, Pentium III (Tualatin), Core Solo, or perhaps all 32-bit machines are next on the chopping block?
Rust, the "secure" language used for firefox and librsvg, no longer work on AthlonXP, Athlon, Pentium III (Katmai and older), Pentium II, and anything older. Because of rust's decision to call "i686" at least a Pentium 4 (with SSE2), these older machines have been left out to pasture. Not sure how hard it is to remove SSE2 instructions from rust's instruction scheduler and still produce a working binary...
I've been depending on these old machines to keep on working as they still share the same instruction set...or seemingly do, until people actually force one to have SSE2.
librsvg is significant as it's a component of gtk+ -- which is used by xfce4 and gnome desktop environments. Looks like KDE or lxde may need to be looked at, and even KDE with its dependency on QT5 and QT5's insistence on having SSE2 instructions, though that can be worked around.
So I guess the original P4, Pentium-M, Pentium III (Tualatin), Core Solo, or perhaps all 32-bit machines are next on the chopping block?
Comment