365 karma · joined October 7, 2024
Its quality seems to vary wildly between various subjects, but annoyingly it presents itself with uniform confidence.
The engineering solution approach doesn't seem to be fundamentally different to speed cameras.
1. use rr for debugging your binary wheel, you can set up watchpoints, and reverse step/continue from the segfault.
2. compile and run your wheel with sanitizers (ASAN, UBSAN).
I rarely use valgrind so I can't comment on that.
What's described here is over-generic code, instead of KISS and just keeping an eye on extensibility instead of generalizing ahead of time. This can happen in any paradigm.
As for generating independent fair coin flips of indefinite length, none of the PRNGs qualify.
And Linus is usually much more critical in what gets into master when it comes to other people's contribution, let alone into an RC.
There is also the complication of composite video signals, where you can't treat pixels as linearly independent components.
What's "the bifurcated reservation API"?
I wonder why it doesn't work this way.
> Under normal circumstances your email client (MUA) connects to your email service provider (MTA), which then sends the email to the MTA of the recipient. So the IP of your MTA (email hosting service), not your MUA (your computer) is exposed.
This is incorrect, most email providers' MTA includes the MUA's IP address in the headers.