quotemstr

8 ms·

151.
by quotemstr 3mo ago
I read the linked post. You're not making a good argument. The authors aren't arguing that a mmap database is worse because it's "more complex". They are arguing it must work with less information. You haven't
152.
by quotemstr 3mo ago
> The best you will ever do, even with full application knowledge and complete control of the machine, is an LRU cache replacement algorithm First of all, even the kernel can do better than simple LRU. We have MGLRU now for example. That
153.
by quotemstr 3mo ago
Sounds like the northern part of the lake doesn't have much of an ecosystem anyway, so why not start there?
154.
by quotemstr 4mo ago
You're right about that. Linux needs a way for userspace processes to participate in the kernel's shrinker system for reclaiming memory under pressure. Watching memory PSI is too coarse. MADV_FREE is too complicated and indiscrimi
155.
by quotemstr 4mo ago
And that's adequate for casual programs. LMDB is big and serious enough to warrant the extra complexity (which, to be fair, is significant) of userspace buffer management. LMDB does the work once and all users benefit.
156.
by quotemstr 4mo ago
I've never understood the fascination some people have with mmap. Memory-mapped file IO is just a RAM cache combined with a hidden system call (a page fault) to fill the cache. You can do the same thing yourself by using O_DIRECT to fi
157.
by quotemstr 4mo ago
Memory encryption is secure under a certain threat model. It makes cold boot attacks, DIMM transfer attacks, and rowhammer much harder to pull off. It doesn't protect against everything and doesn't pretend to do so, but IMHO it&#x
158.
by quotemstr 4mo ago
It's because of vulnerabilities like this that I enable Intel's "total memory encryption" feature. No plaintext leaves the CPU package. DIMM swap attacks become useless. Moreover, it's basically free: the cryptograp
159.
by quotemstr 4mo ago
Nobody's used state power to mandate peptides and social media censorship to reports of adverse effects. As many of us said at the time, the mandates weren't worth the destruction of public trust, especially because the vaccine wa
160.
by quotemstr 4mo ago
Not if you have an address space conflict, e.g. if you want to move a stack within a single process. Linear addresses are relative to a whole address space root.
161.
by quotemstr 4mo ago
> What ruins this for C is the existence of pointers. Stacks aren't freely relocatable since pointers into the stack could exist. I sometimes wonder what computing would be like if the 80286 hadn't sucked, if segmentation had w
162.
by quotemstr 4mo ago
zkVMs (of which RISC Zero is one example) do not require a TEE. That's the whole point: the privacy properties come out of the math. Basically, nowadays, once you and I can agree on the text of a program, you can run the program on y
163.
by quotemstr 4mo ago
RISC Zero verifies that an exact computation was performed. What would be the point of the system otherwise? If you're starting from this incorrect premise, you're going to arrive at an incorrect conclusion. > Single purpose ci
164.
by quotemstr 4mo ago
It is good that Microsoft Vega is popularizing zero-knowledge identity-based attestations. It's unfortunate that they're doing so in a relatively inflexible way. I wish the Vega people had oriented their work around general-purpos
165.
by quotemstr 4mo ago
<something>.duckdns.org. works fine, and being "beholden" to ICANN is no worse than being a client of one of the big traditional gTLDs. If you want "one person, one name", well, .name is there for that. It's a
166.
by quotemstr 4mo ago
ICANN and its consequences have been a disaster for the internet namespace.
167.
by quotemstr 4mo ago
And you needed a gTLD for this task why?
168.
by quotemstr 4mo ago
It doesn't have to be, FWIW. We have all the technology we need to decouple attribution from identity. We can achieve efficient and mathematically perfect unlinkability. Yet the powerful continue to insist on "papers, please"
169.
by quotemstr 4mo ago
Huh? Blocking sudo works just fine. I don't know why everyone is acting like sandboxing tool uses is contrary to the laws of God and man and therefore we must adopt devcontainers and VMs and such to run agents. ... Sandboxes work JUST
170.
by quotemstr 4mo ago
> Hopefully they never actually implement this pointless feature because it will only give people a false sense of security given the unpredictable nature of LLMs. How could something like this even be enforced? You run everything the mo
171.
by quotemstr 4mo ago
> You can do this now: change the file permissions such that the user you run codex as can't read them, or run codex in a container without those files mounted. That's quite inconvenient. I want to run my coding agent in a rest
172.
by quotemstr 4mo ago
I have a local patch that reads a new config section that looks like this: [sandbox.always.filesystem] "~/.config" = "none" "~/.config/git&quot
173.
by quotemstr 4mo ago
> If configuration expects a regex for some reason, that's a signal that you're expected to be a programmer to use the software 1) What? Only programmers are expected to use grep? What? That's absolute nonsense. Even prog
174.
by quotemstr 4mo ago
Because I don't know what language your program is even written in! Why should I know or care that you chose, e.g. TypeScript, when I'm trying to use or configure your program and don't know how to spell this or that regex co
175.
by quotemstr 4mo ago
It drives me nuts when a developer documents something or other as being a "regex" but doesn't mention which dialect of regulation expression he's talking about. This habit is particularly common in the Rust, JavaScrip
176.
by quotemstr 4mo ago
And we disagree on how best to gain control of latency. Some say that the way to gain control of memory management latency is to track object-level allocations locally using malloc/free-style APIs, arenas, and so on. IMHO, low tail lat
177.
by quotemstr 4mo ago
Various GCs can go faster now too. JEP 376 talks about hundreds-of-microsecond work done in pause now that GC no longer has to scan the whole stack. That said: 1ms? 1ms is getting into the sorts of latency the OS and hardware impose on your
178.
by quotemstr 4mo ago
Smart, honest people can have sincere and earnest disagreements. I believe the manual-memory-management people are mistaken. That's not to say they're stupid: it means I believe they're going down the wrong path, as smart peo
179.
by quotemstr 4mo ago
ZGC is extremely good work. https://wiki.openjdk.org/spaces/zgc/pages/34668579/Main > ZGC performs all expensive work concurrently, without stopping the execution of application threads for more than
180.
by quotemstr 4mo ago
The charitable explanation is the authors lack the time to rebase onto something more modern.

More ›