1 karma · joined March 21, 2026
So basically rustc_codegen_gcc and cranelift can compile code that don't with LLVM and then introduce (or solve) new bugs?
This Deployment has been disabled.
Your connection is working correctly.
Vercel is working correctly.
402: PAYMENT_REQUIRED Code: DEPLOYMENT_DISABLED
It imply the existence of some sets that cannot be Lebesgue measured (which is an generalization of width, volume, etc for arbitrary sets, also generalization of probability for arbitrary sets)... but it's not possible to present a single example of those non measurable sets, only prove that they exist.
And it's possible to construct an alternative theory with the axiom of determinacy, then any subset of R is measurable.
* https://en.wikipedia.org/wiki/Axiom_of_choice * https://en.wikipedia.org/wiki/Axiom_of_determinacy * https://en.wikipedia.org/wiki/Lebesgue_measure
So, how does the author got hold of Wii's code, is it publicly available or was it some kind of reverse engineering?
While plain text connections would affected only users using the plain text connection.
See comment from https://news.ycombinator.com/item?id=38047633
Quite often I saw quite similarly absurd stuff coming out of those translations, so I'm not at all surprised at this.
At this point in time, if you use Tokio, won't basically everything mainstream work? At least that has been my experience so far.
It seems all about the hope that you can keep the user engaged long terms. I don't blame them, competition for user attention is brutal in the age of the SEO content farms, oligopoly of social networks and the "Tyranny of the Marginal User" as posted here a few days ago.
But probably way less effective now that most users seem overwhelmed by so many push notifications and instinctively learned to mass ignore or dismiss them (myself included, just randomly noticed that background habit a while ago). And then we end-up with piles of installed unused apps just like lost websites in the browser history.
Granted that the supply chain attack defense would fall on the hands of the users of the library. Unless the library writer aggressively pins of dependencies on the Cargo.toml (not the default semver action), problematic, but at least Cargo allows multiple versions of dependencies on a program, on Python for instance this is much complicated scenario (but still the smallest of the dependencies problems there).
but at the same time, they put ToS that you may not train a new LLM using the output of their LLM...