SMS is a proven standard that works reliably.

lol

I tried RCS twice, in both cases the other end did not receive my message or at a later time.

This is not indicative of how well RCS will work as its widespread adoption continues to mature. I do understand your frustration; I just would expect the growing pains to last much longer. Remember how shitty USB C was for the first few years?

Apple forked WebKit from KDE back in 2001. For all intents and purposes, they didn’t switch to it; they developed it.

Counterpoint: SMS shouldn’t exist, and RCS is our best shot at replacing it right now

arm still needs a custom kernel and conpletely different drivers to even boot, because every manifacturer can implement it completely differently.

Dunno why you’re getting downvoted, this is correct. ARM makes comparatively very expensive to maintain an OS over a variety of CPU models. The specialization required by each Cortex revision (and beyond that, each manufacturer adaptation) is too intense for a world trying to conserve resources.

x86 hardware is standardized in a way where you don’t need to port an os to them, it just runs with generic drivers.

That being said, I’m honestly shocked your friend doesn’t run into issues. Several ISA extensions have been released for x86 since the Core 2 Duo days, and I have to imagine software incompatibilities appear semi-frequently. Running Windows 10 on that can’t be a good experience.

If there was an option that was presented to users once the device got below 80% battery health to slow down the system to make daily batter life longer

This isn’t why they did it. Degraded Li-ion batteries cannot sustain their rated voltage at high currents due to increased internal resistance. Sufficiently undervolted CPUs/memory cells produce errors (specifically bit flips), which can rather quickly lead to memory corruption and a crash.

Reducing the CPU frequency (thereby reducing the peak current draw) is practically necessary in the face of a degraded battery. Various laptops were infamous for not doing this, because it resulted in a ~20-30 minute battery life, as the voltage drop became too great once the battery charge drops below 80-90%. Within the context of a smartphone, neglecting to use the remaining 80-90% would make it basically useless.

What Apple (and the rest of the smartphone industry, at this point) really needs to do is make their batteries replaceable.

Can you evaluate the directory tree of a tar without decompressing? Not sure if gzip/bzip2 preserve that.

Or they’re interpreting the law as written without context so they can get home by lunch, just like every other originalist.

Until Cloudflare responds to the post, it is IMO most beneficial to assume that the OP is being truthful and forthright. Doing so puts pressure on Cloudflare to either clarify or rectify the situation, whereas treating Cloudflare as though they are above suspicion accomplishes nothing.

After all, OP is very much the little guy here.

Because Microsoft cares so much about an 18.6K-member community called “linuxmemes” on a small federated Reddit alternative known for being filled with die-hard Linux fans and furries?

I’ve never really thought about this before, but const volatile value types don’t really make sense, do they? const volatile pointers make sense, since const pointers can point to non-const values, but const values are typically placed in read-only memory, in which case the volatile is kind of meaningless, no?