dap

6 ms·

31.
by dap 10mo ago
Open-source ransomware?
32.
by dap 10mo ago
I hear that, but it feels kind of empty because I haven't seen much discussion of that cost/benefit analysis (both of poisoning itself and of the change to the default behavior, which has its own costs and benefits). I take it as
33.
by dap 10mo ago
This is a false dichotomy. Not every technique needs to work in all cases in order to be useful. This seems analogous to arguing that because seat belts don't save the lives of all people involved in car crashes, and they're kind
34.
by dap 10mo ago
You seem to keep making the implicit assumption that because people are using `unwrap()`, they must not care about the poisoning behavior. I really don't understand where this assumption is coming from. I explicitly want to propagate
35.
by dap 11mo ago
That’s not surprising to me, but it’s not much of an argument for changing the default to be less safe. Most people want poisoning to propagate fatal errors and avoid reading corrupted data, not to recover from panics. Edit: isn’t that an a
36.
by dap 11mo ago
At my last job, we only updated dependencies when there was a compelling reason. It was awful. What would happen from time to time was that an important reason did come up, but the team was now many releases behind. Whoever was unlucky
37.
by dap 11mo ago
I’d strongly recommend the documentary “Behind the Curve”. The close look at people in (not quite a cult) gave me a visceral appreciation for what draws people to it (it provides acceptance for people who sorely lack it) and why it can be s
38.
by dap 11mo ago
I'm not sure if this is serious or not, but to take it at face value: the value of this sort of thing in Rust is not that it prevents crashes altogether but rather that it prevents _implicit_ failures. It forces a programmer to make t
39.
by dap 11mo ago
I would say it can go further than that: Rust enables you to construct many APIs in a way that can’t be misused. It’s not at all unique in this way, but compared with C or Go or the like, you can encode so many more constraints in types.
40.
by dap 11mo ago
I definitely hear that! To keep it in perspective, though: we've been operating a pretty good size system that's heavy on async Rust for a few years now and this is the first we've seen this problem. Hitting it requires a bu
41.
by dap 11mo ago
> So how exactly did they bring about the impossible? They put an await call inside the critical section. The part of the code base that is not allowed to be subject to arbitrary delays. Massive facepalm. I'm not sure where you got
42.
by dap 11mo ago
Don't do ... what, exactly? The RFD answers this more precisely and provides suggestions for alternatives. But it's not very simple because the things that can cause this are all common patterns individually and it's only t
43.
by dap 11mo ago
Your confusion is very natural: > It's more typical in my experience that the act of granting the lock to a thread is what makes it runnable, and it runs right then. This gets at why this felt like a big deal when we ran into this.
44.
by dap 11mo ago
I think you misunderstand the problem. The only purpose of the sleep in this example is to control interleaving of execution to ensure the problem happens. Here's a version where the background task (the initial lock holder) only run
45.
by dap 11mo ago
Is it possible that those names are intentionally chosen and actually do carry meaning?
46.
by dap 11mo ago
(author here) Although the design of the `tokio::select!` macro creates ways to run into this behavior, I don't believe the problem is specific to `tokio`. Why wouldn't the example from the post using Streams happen with any othe
47.
Amazon to Lay Off Up to 30k Corporate Workers(wsj.com)
6 points by dap 11mo ago|2 comments
48.
by dap 1y ago
> Let’s take God’s punishment unto man from the events of Eden for a moment. > If you don’t hold a creature given morality accountable, then that creature is fundamentally is the same as a creature that was not given morality. In the
49.
by dap 1y ago
> Todoist: Great until I realized I was gaming the points system instead of doing actual work. Turns out completing “drink water” 8 times a day doesn’t make you productive. This is such a strange conclusion. Just... stop using the point
50.
by dap 1y ago
Folks are criticizing this as too much or coming from too much anxiety. I might have agreed before owning a home and having kids. But I totally get it. A typical week involves dozens of random tasks like those you mentioned. Then there&
51.
by dap 1y ago
Sorry I didn’t say it sooner: thanks for sharing this post! And for your work on Matrix. (Sorry my initial post focused on the negative. This kind of thing brings up a lot of scar tissue for me but that’s not on you.)
52.
by dap 1y ago
>> If you ran into a problem like this on ZFS, for example, you'd have very high confidence about whether the disk was at fault > Would we, though? I'll admit to not being that familiar with ZFS's internals, but I&#x
53.
by dap 1y ago
The post appears to conclude that this must be a hardware issue because they have no explanation and PostgreSQL and the kernel are too reliable to have data corruption bugs. I've seen data corruption bugs in both databases and the ker
54.
by dap 2y ago
Sure, “just” a machine honed over millions of years and trained on several years of specific experience in this area.
55.
by dap 2y ago
> It's almost as if you'd want to not feed what the patient says directly to an LLM. > A non-trivial part of what doctors do is charting - where they strip out all the unimportant stuff you tell them unrelated to what they&#
56.
Performance Puzzler: The Slow Server(davepacheco.net)
1 points by dap 2y ago|0 comments
57.
by dap 2y ago
> Evaluate "majority" this way: For every/any random binary in a distro, out of all the currently running instances of that binary in the world at any given moment, how many of those need to be profiled? > There is no w
58.
by dap 2y ago
Makes sense. I wasn't exaggerating about recompiling the world, though. Even if we say I'm only interested in profiling my application, a single library compiled without frame pointers makes useless any samples where code in that
59.
by dap 2y ago
I’ve been around long enough to have had frame pointers pretty ubiquitously, then lost them, and now starting to have them again. The dark times in the middle were painful. For the software I’ve worked on, the easy dynamic profiling using
60.
by dap 2y ago
This reads to me like FUD. Isn’t the fraction of profile samples in a prologue heavily workload dependent? And whichever way you go on frame pointers, there are winners and losers to including them by default.

More ›