Slacky wrote:
> On 2016-12-27, Askfor <
ask...@nowhere.net> wrote:
>
>>> The above said, I'm not a programmer, but I strongly suspect that
>>> nothing in the Firefox/Mozilla code itself would be going so low-level
>>> as to directly address the SSE2 registers, and that it would be rather a
>>> compile-time option.
>
> Firefox actually has a bunch of assembly code which is why it is not
> available on most platforms.
>
>> Like it or not 32-bit is going away. There is less and less support for
>> it. 32-bit is perfectly fine for home users, but hardware vendors are
>> making 64-bit, and those who write and/or package software often can't
>> be bothered to maintain two versions.
>
> Until Acroread comes in a native 64 bit version I'm staying with Slack 32.
> If it weren't for application bloat there would be essentially no reason you
> couldn't live with 4GB of RAM for a desktop. Given how much apps like
> Firefox and Acroread use even 16GB feels like a small desktop these days.
Actually, I had problems with 32-bit Acroread on one computer. It kept
throwing some error mentioning Debian !!??? I don't remember exactly any
more.
>
> I have a box for work with a core i7, 32GB of DDR4 and an SSD and it still
> can't run Windows 7 acceptably. Life sucks when you have to run bloatware.
> Linux is getting there. You could say it's already there.
>
Agree
>> I guess this move is more to give additional push to 32-bit users than
>> due to real need. That is progress being pushed down our throats and
>> there are always idiots and vegetables in human form who say that "one
>> has to embrace the change" or something.
>
> If you're talking about Firefox it has to do with most people in denial that
> there is any hardware but Intel. I happen to know there is because I have a
> bunch of it sitting in front of me. But those same people don't realize
> there are any OS besides Windows or Linux so...
>
I am talking about Linux distros and software in general. Yeah, I know
there are ARM, SPARC and others. I worked on 32 and 64-bit SPARCs for
quite a while. Particularly I am talking about 32-bit Intel. At least
there should have been a decent emulation. When 16-bit was going away,
i386 and i486 did decent job running 16-bit apps without extra
compatibility layer.
> They don't want to have platform dependent code for other than Intel x86_64
> anyway. Many of these guys have day jobs so it is inevitable.
>
Nobody in right mind wants any platform dependent code.It's a liability.