You don’t necessarily have to write a non-transitive cmp() function willingly, it may happen that you write one without realizing due to some edge cases where it’s not transitive.

And have you ever seen a bolt fall off a plane you were flying on?

But I just need to find one that doesn’t and by an open source Android there will always be an image to flash.

Unfortunately sooner or later Play Integrity will make this unfeasible in practice.

For that usecase rustc_codegen_gcc works too and is much more likely to be mature soon.

That’s why I said unstable operations. Addition is considered a stable operation (for values with the same sign)

TBF the error can become that big if you do a bunch of unstable operations (i.e. operations that continue to increase the relative error), though that’s probably not what is happening here.

From their github:

NOTE: When Qt is installed on the system, the native style uses Qt’s QStyle to achieve native looking widgets.

I’m not that familiar with KDE’s styling, but if I remember well it should just be a Qt style, so it should work.

Regarding rewriting Dolphin, I think in theory you could do that, in practice it’s probably pretty challenging given the amount of features Dolphin has.

slint has a good native look that resembles QT

It doesn’t just resembles QT, it uses QT as backend.

As long as many important games fall into that 10% many gamers won’t consider Linux.

Not to mention Adobe/Office/CAD suites that will prevent others from switching.

And finally most pcs are sold with windows preinstalled and the vast majority of people don’t even know that other OS even exist.

QEMU have qemu-user (if you didn’t know), which basically Rosetta for Linux, but with a good performance hit when testing cross-compiled code.

Aren’t Box64 and FEX faster though?

Vs Codium is the open source version. Vs Code is based on Vs Codium but with the addition of closed source telemetry and the extensions marketplace.

Every atom has energy in it, regardless of whether it is radioactive or not. Radioactiveness just makes it relatively easy to extract that energy. But even then, it’s not that simple, not every radioactive material is good for a nuclear reactor. If the fuel absorbs too many neutrons without fission, or produces elements that do, then it can become poison for the reactor. And if it, or the elements it produces, emit very few delayed neutrons and very quickly then it makes it harder to keep the reactor in a sub-critical state (i.e. it makes it harder to not make it explore). Often for these reasons you can’t fully use reprocessed fuel, and instead you have to mix it in low percentages with normal fuel. Reprocessed fuel is also harder (thus cost more) to produce since you have to work with highly radioactive materials.

I did that a couple of times, but it was more like “I don’t want to grind all of this stuff, I want to skip to the fun part”. Also, it’s morally different because it impacts nobody else.

I wonder why this is not a problem for pcs though

Hey, I switched to Firefox because I liked its UI better (after Quantum though)

Though let’s be honest, this is not something generally available.

I agree with you, but it’s still a fact that that sponsorship make up most of Mozilla’s income. And if Google gets broken up then will they still care about that?

You’re right, but the argument was that it wouldn’t be that disruptive, and that’s not true.

As for the browser, I’d be glad if Chrome died. We need more browsers. Chrome dying would force all of the derivatives to do something else. Vivaldi, edge, brave, etc would all need to either switch to Firefox or a project for a new browser would begin

Firefox is currently kept alive by Google, which pays $500M/year to Mozilla in order to have Google Search as the default in Firefox and to not let Google Chrome become a monopoly on paper too. Break Google and it would probably die.

Creating “more browsers” (browser engines I would add, we already have enough browsers) is not an easy task. The specification that needs to be implemented is massive, and doing so efficiently is even more complex. It would be a waste of resources to have many browser engines, not to mention the confusion in the webdev community when you suddently have to work around many more bugs in the implementations.

Yeah, and none of them let you keep your existing @gmail.com address. Which means you’ll have to update it everywhere. That’s the massive problem.