[flagged]
I hate compilers
161–170 of 182 posts
Re: I hate compilers
#162> There are a shocking number of ways to accidentally create nondeterministic output when doing C/C++ development. One of the easiest is to use the builtin __DATE__ and __TIME__ macros to stamp a build with the time the compiler was executed at: Am I missing something here? Yes, if you use a feature that intentionally inserts the build time and date into the code, the every build is going to be different. That's the…
"One of the easiest" It's meant to be a trivial counterexample. Like saying "-1" to the claim "there's no number smaller than 0" to someone who's not familiar with math, the author is saying "build-dependent macros" to the claim "compilers are deterministic" to someone who might not be familiar with compilers.
Re: I hate compilers
#163Earlier quoted context omitted.
No it's not dumb, but I don't get how it manages to be so light still. Like I visit an Anubis-guarded site and barely have to wait. Scrapers really see that little CPU usage or wall time and back off? Or maybe that's just cause I'm not visiting sites that are under attack.
It chooses the challenge weight based on signals. If your phone looks like a phone from a residential IP you get a simple challenge. If you then spam requests you might get another, harder, hallenge appear. If you have a data center IP and look like bot traffic you get a hard challenge out the gate. AFAIU after looking at their docs several months ago.
Re: I hate compilers
#164[flagged]
Re: I hate compilers
#165[flagged]
If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
Re: I hate compilers
#166Earlier quoted context omitted.
"One of the easiest" It's meant to be a trivial counterexample. Like saying "-1" to the claim "there's no number smaller than 0" to someone who's not familiar with math, the author is saying "build-dependent macros" to the claim "compilers are deterministic" to someone who might not be familiar with compilers.
A trivial counterexample to what? The antecedent of "one of the easiest" was "ways to accidentally create nondeterministic output." One even the most charitable reading I can muster that still seems to me to presume some pretty abject stupidity.
Re: I hate compilers
#167Earlier quoted context omitted.
I don’t get how people believe there’s a PoW function that both: 1. Allows access in reasonable time/battery use to me on my phone 2. Poses any meaningful challenge to the most compute-resourced organizations on the planet I wonder how many cumulative hours of human life have been wasted waiting on Anubis.
> I wonder how many cumulative hours of human life have been wasted waiting on Anubis. "How dare that mugging victim fight back". The choice is not between Anubis and no Anubis, the choice is between Anubis and my website going offline because I can't afford the $400/month that AI scrapers would cost me (yes, I checked, and yes, that's the real figure) if Anubis wasn't in front.
Re: I hate compilers
#168Earlier quoted context omitted.
Unless you use a flake or the project has a flake.nix
There is nothing in Nix that magically makes concurrent builds with completion-order-dependent outputs come out deterministic.
Re: I hate compilers
#169> There are a shocking number of ways to accidentally create nondeterministic output when doing C/C++ development. One of the easiest is to use the builtin __DATE__ and __TIME__ macros to stamp a build with the time the compiler was executed at: Am I missing something here? Yes, if you use a feature that intentionally inserts the build time and date into the code, the every build is going to be different. That's the…
In a parallel non–Euclidean dimension, perpetrators go the other way and have their victims build with -j1 reproducible builds.