jabjoe's comments

Interesting. The one time I ended up writing assembly was because of SIMD. I was speaking about it recently and had forgotten it was because SIMD instructions, so nice to be reminded. However, that one time, I also ended up finding the right syntactic sugar, to get the compiler to do it right. If I remember right it was all down to aliasing. I had to convince the compiler the data wasn't going to be accessed any other place. It wasn't working that out itself, so it didn't know it could use the SIMD instruction I was. Once I found this and the right non-standard extra key words, the compiler would do it right. So I ended removing the assembly I had written.

This isn't working for me. I'm yet to find a way back to compact mode. Which basically means Reddit on phone is unusable. The information density is terrible on a small screen without compact mode. All pictures shouting for attention.

Edit: turns out the closed the backdoor into compact mode. Enshittification is now in full swing.

> Also, by the time Intel stopped pushing x86 in mobile devices they were producing chips that were competitive with ARM chips when it came to power draw.

People forgot this. It was price that killed Intel in this space. They couldn't get the price down to ARM chips. They subsidized hard to get even close, but it ended up just costing them too much just to have even a presence.

First off, I run Linux ARM code on x86 quite often, using qemu-system-arm and chroots.

Secondly, you only rarely need to because everything you use is in the package management system, thus compiled for the platform you are on (and against the same versions of the libs as everything else, thus only one, up to date, version of each lib and only the libs you need).

The only reason I've sometimes do qemu-system-arm and chroots is I'm a software developer often working on ARM Linux (from x86 Linux).

Third, I will also point you to: https://wiki.debian.org/Multiarch

But normally, you use a pure system. All 32bit, all 64bit or all ARM, etc etc. Closed crap can muddy your system, for instance requiring (normally old) versions of 32bit libs on a 64 bit system, but the solution to that is to not use closed crap.

Yes, MOC and QT's C+++ is really an awful thing. Copperspice being just normal C++ is interesting. Have to see what happens. But for me, C is where my heart is, so there is still two + that need to go for me. ;-)

I've found it locks up on Linux sometimes. Like I found Clementine when I was stuck on Windows. Having worked with QT, and it's asynchronous'ness, I can see it's easy to make dead lock mistakes, and I think that is probably what is happening.

You can not expect them to understand the ins and outs of every purchase. You judge a society by how it looks after it's people. You are arguing to leave them to the wolves.

No. Government needs to have laws against this. We can't leave it up to ignorant and fickle consumers. This is a failure of the system of law, thus government. Consumer action is no substitute. Voting with wallets is not equal in anyway to voting. And never should be. We shouldn't be trying to herd consumers to punish companies, we should be asking governments to do their job.