dwattttt

18 ms·

301.
by dwattttt 11mo ago
> what would be the benefit of the brain looking inwards and constantly questioning itself? When what you think matters. An animal that questions its belief "there is no tiger behind that bush" and finds a tiger lives longer th
302.
by dwattttt 11mo ago
That "things were better in the old days, all this safety culture is pointless" overlooks the tragedies we became inured to back in those days? I cannot count the number of times I've heard "we never bothered with that&q
303.
by dwattttt 11mo ago
Have you considered not tying your encryption keys to your child's online activities? I can understand the thrill of danger, but I'm not that much of a gambler myself.
304.
by dwattttt 11mo ago
I marvel at your ability to consider cryptographers as inhuman machines, despite evidence to the contrary.
305.
by dwattttt 11mo ago
> It looks like changing the permissions triggered creation of a new feature file, and it was ingestion of that file leading to blowing a size limit that crashed the systems. That feature file is generated every 5 minutes at all times; t
306.
by dwattttt 11mo ago
It's relevant when you have more complex objects, such as ones that contain independent mutexes that lock different sections of data. You want the object to present its valid operations, but the object could also be constructed in sing
307.
by dwattttt 11mo ago
A more direct analogy is right there; your Phillips head screws cam out more easily than Torx. Everyone who wants screws that don't shred as easily moves to that weird 6 pointed star pattern, and your Phillips head screwdrivers are sud
308.
by dwattttt 11mo ago
Since it took me a minute to realise... glib vs MSVCRT are the keywords to the joke.
309.
by dwattttt 11mo ago
The maybe unexpected point is that if you know you're the only one who has a reference to a Mutex (i.e. you have a &mut), you don't need to bother lock it; if no one else knows about the Mutex, there's no one else who cou
310.
by dwattttt 11mo ago
> ucs-detect automatically tests the Unicode version and support level... The first line of the site suggests otherwise.
311.
by dwattttt 11mo ago
A solution would be to require hotels to carry insurance for this event.
312.
by dwattttt 11mo ago
Having been close to someone who went through the PhD process to a career in research, this is a sadly common but romantic and incorrect view of science as practiced in the world today.
313.
by dwattttt 11mo ago
Yes, that's an existing soundness hole in the compiler. You won't accidentally code it up yourself though. If the bar is "deliberately malicious code results in a segfault", get back to me when they fix memcpy(0x1000
314.
by dwattttt 11mo ago
By first party support, would you be expecting a Rust toolchain shipped in the NDK, or maybe Rust bindings shipped in the NDK? I could see the latter, although I'd still question whether they should be special cased in terms of a Rust
315.
by dwattttt 11mo ago
> And then the rest of us have a data point that we think we can trust, when in reality, it's just cherry picked data being used to convey an opinion. Calling what Google did here "science" and cherry picked is quite a dis
316.
by dwattttt 1y ago
Statically asserting at compile time that all memory access are either in-bounds, or will result in a controlled unwind or exit of the process, guarantees there are no memory safety violations. We understand you're saying it's not
317.
by dwattttt 1y ago
I've used many, debugging both dumps and live processes. And I'll take a compiler that highlights the problem at build time any day.
318.
by dwattttt 1y ago
> It seems obvious that with hardware-level memory safety on the way[1], just gradually modernizing existing C and C++ codebases to take advantage of safer constructs (like smart pointers or checked arithmetic) makes much more sense than
319.
by dwattttt 1y ago
At compile time, Rust guaranteed memory safety here by ensuring a runtime check was present, which your code triggered, resulting in a panic. A panic is not a violation of memory safety; if you wanted to violate memory safety you'd nee
320.
by dwattttt 1y ago
Ironically you're correct, and yet I'm still closer to the original meaning than the typical quotation.
321.
by dwattttt 1y ago
It doesn't, but at that point you're not referencing what a person meant, you're saying something they didn't intend with their words. You might as well make your point with your words, instead of misleadingly quoting so
322.
by dwattttt 1y ago
"Those (the Penn family) who would give up essential Liberty (money & power), to purchase a little temporary Safety (a veto over a taxation dispute, trying to raise money from the Penn family), deserve neither Liberty (said money &
323.
by dwattttt 1y ago
Archives of published MS SDKs show they were using the feature in NT 3.1's public headers in 1993, so it's at least that old. https://archive.org/details/win32-sdk-final-release-nt-31
324.
by dwattttt 1y ago
If you have the Rust toolchain installed, installing is as simple as e.g.: cargo install ripgrep which will result in ripgrep being downloaded, compiled, and copied to a per user directory that's included on PATH as part of the
325.
by dwattttt 1y ago
They're doing one site less now
326.
by dwattttt 1y ago
While IANAL: even people who have done wrong deserve to be treated fairly. "Cognitive dissonance" has nothing to do with representing someone. Businesses don't have to delude themselves to succeed either.
327.
by dwattttt 1y ago
From the link, mlockall with MCL_CURRENT | MCL_FUTURE > Lock all pages which are currently mapped into the address space of the process. > Lock all pages which will become mapped into the address space of the process in the future.
328.
by dwattttt 1y ago
If you're getting this far into the details of your memory usage, shouldn't you use mlock to actually lock in the parts of memory you need to stay there? Then you get to have three tiers of priority: pages you never want swapped,
329.
by dwattttt 1y ago
> spooky-action-at-a-distance type errors Global type inference is literally this. Inferring types leaves gaps in the typing information, being global means the gaps can be arbitrarily large, and so a type conflict could theoretically sp
330.
by dwattttt 1y ago
And Rust: https://rustc-dev-guide.rust-lang.org/type-inference.html

More ›