HackerTrans
TopNewTrendsCommentsPastAskShowJobs

whyever

no profile record

comments

whyever
·il y a 2 mois·discuss
There was Quelle, Europe's largest mail-order and retail company. They were excited about mailing their catalogue on CD-ROM, but slept on the Internet. In 2009, they went bankrupt.
whyever
·il y a 3 mois·discuss
LLMs are vulnerable to prompt injection attacks, so I'm not sure they are in advantage.
whyever
·il y a 8 mois·discuss
Note that N=1 for the memory safety vulnerabilities they had with Rust, so the error of the estimated average number of vulnerabilities per LOC is quite large.
whyever
·il y a 8 mois·discuss
It's missing which point?
whyever
·il y a 9 mois·discuss
I agree, but https://www.pcg-random.org/ still advertizes PCG as "challenging" to predict, and critizises other RNGs as predictable and insecure.
whyever
·il y a 10 mois·discuss
Yes, but this relation does but apply to statistical mechanics and statistical physics, they mean the same: https://en.wikipedia.org/wiki/Statistical_mechanics

What is included in "statistical physics" that is not included in "statistical mechanics"?
whyever
·il y a 10 mois·discuss
They are synonyms.
whyever
·il y a 10 mois·discuss
Signal asks you to repeat the key immediately before even enabling backups. It cannot fail much later unless you modify the digit after the check.
whyever
·il y a 10 mois·discuss
That's a good question! Especially after Frank McSherry's COST paper [1], it's hard to imagine where the sweet spot for Spark is. I guess for Databricks it makes sense to push Spark, since they are the ones who created it. In a way, it's their competitive advantage.

[1]: https://www.usenix.org/system/files/conference/hotos15/hotos...
whyever
·il y a 11 mois·discuss
> With that access you can also "do" things, like sending messages or delete stuff.

If you break E2E encryption, you can likely also impersonate and "do" things.
whyever
·il y a 11 ans·discuss
In Python you basically get undefined behavior when encountering NaNs while sorting, Rust let's you choose. This seems much more reasonable to me.
whyever
·il y a 11 ans·discuss
Rust's way is more flexible though: You can choose how to treat NaNs, in Ruby you have to fail.