dwattttt

55 ms·

691.
by dwattttt 2y ago
atexit enters the chat
692.
by dwattttt 2y ago
> your model would just learn to interpolate between geographically proximate locations At a particular scale, this is entirely correct; if what I'm looking for is 'large', a measurement 1m away from a known hit would also
693.
by dwattttt 2y ago
He stated the higher security model he uses; a paper book. As well as his threat model, which is pretty coherent and relevant in this modern age. I'd love to see someone "hack" his book, it would be quite the impressive hack.
694.
by dwattttt 2y ago
Rust is experimenting with "portable SIMD": https://doc.rust-lang.org/std/simd/index.html It defines a generic `Simd<T, N>` type, expressing "This is a vector of T elements (such as i8), and i
695.
by dwattttt 2y ago
> AI companies contend that it's fair use It's a good thing they don't train on copyrighted material from jurisdictions that have something other than "fair use", such as Australia's "fair dealing"
696.
by dwattttt 2y ago
> unauthorized use of any kind was already forbidden Is a funny sentence to have to say. Is unauthorized use also unauthorized?
697.
by dwattttt 2y ago
You're thinking of C; Rust forced that somebody to write unsafe near it to create the bug.
698.
by dwattttt 2y ago
> the problem might not be so localized as the notion of "only auditing unsafe blocks is sufficient" implies It depends on what you consider "problem" can mean. An unsafe function needs someone to write unsafe in orde
699.
by dwattttt 2y ago
I expect this is referring to Intel's proposed X86S spec: https://www.intel.com/content/www/us/en/developer/articles/t...
700.
by dwattttt 2y ago
As I mentioned else-thread: it doesn't matter as much which option is chosen, so long as everyone agrees. If everyone agrees that LF on its own is enough (and we stop sending CR's to make sure it's not part of whatever comes
701.
by dwattttt 2y ago
Pragmatic choices is what Postel is known for now, and it makes for a pretty confused world when everyone makes different pragmatic choices.
702.
by dwattttt 2y ago
If you're using tools that only support one particular line ending, the solution isn't to convert your source automatically in the repo, it's to know your source is always stored in one format, and convert it back/forth
703.
by dwattttt 2y ago
But what's bare-0ah-tolerant? Accepting _or_ ignoring bare 0ah's means you need to ensure all your moving parts agree, or you end up in the "one bit thinks this is two headers, others think it's one header". The onl
704.
by dwattttt 2y ago
But no one expects 0ah to be sufficient. Change that expectation, and now you have to wonder if your middleware and your backend agree on whether the middleware filtered out internal-only headers.
705.
by dwattttt 2y ago
Just because you have all of those costs already doesn't make them go away. If you're cross-subsidising the H100 access with the rest of a profitable business, that's a choice you can make, but it doesn't mean it's
706.
by dwattttt 2y ago
If you already have the H100s, renting access to them at a loss isn't better. Throwing them in the trash will lose you less money.
707.
by dwattttt 2y ago
That particular trick is known as fixed point arithmetic (not to be confused with a fixed point of a function)
708.
by dwattttt 2y ago
> The article talks about wstrings for good reason. If you're converting narrow strings, you don't need to be this fancy. Just loop over the string and edit it in place. Since you mention narrow strings in the context of wstrin
709.
by dwattttt 2y ago
The potential problem though is that the surviving standard may have been the best for a reason that's no longer relevant. There are certainly decisions that have been made over the last 30 years that don't make sense in light of
710.
by dwattttt 2y ago
Ah, security via the honour system. Unbeatable
711.
by dwattttt 2y ago
If you use type checking, the breakage occurs when you introduce the change: the author of the change is the one who can figure out what it means if 'foo' is no longer being passed into this function. If you're duck typing, y
712.
by dwattttt 2y ago
Not anymore. The time travel issue was fixed with time travel.
713.
by dwattttt 2y ago
That's the part I was curious about; whether there would've been a helpful cache impact, if not for modern Spectre prevention.
714.
by dwattttt 2y ago
> the overlapping is useless since everything beyond the next mispredict is useless as it is on the bad path Is this a consequence of Spectre et al mitigations?
715.
by dwattttt 2y ago
I don't as a rule web dev, so when I do I fall into the same category as the author: lowest effort to get something mostly right. An explanation for "why bother try to have a low effort web server in Rust?" that I haven'
716.
by dwattttt 2y ago
https://github.com/BurntSushi/aho-corasick I've had a lot of fun playing with it, it was very nice & simple to use. It's also foundational in the Rust ecosystem, so it's well maintained.
717.
by dwattttt 2y ago
Invention isn't some incredible rare gift; putting two things together that you've never personally seen done before is novel, even if it's food.
718.
by dwattttt 2y ago
I believe these are the issues: https://github.com/golang/go/issues/52690 https://github.com/ziglang/zig/issues/14989
719.
by dwattttt 2y ago
You can have multiple incompatible dependency versions imported by the one create; you have to give them different names when declaring them, but it works fine (I just tested it). It follows the approach of "objects from one version of
720.
by dwattttt 2y ago
Even being run on the same machine doesn't guarantee two independent processes agree on C struct layout compiled from the same source. For one, you could have something as simple as one compiled for 32bit, one 64, but even then compile

More ›