boris

7 ms·

1.
by boris 1mo ago
It is lz4. While all that you say about disk being slow makes sense, measurements show that in this specific situation disabling compression improves performance by a little. My hand-wavy explanation is that freeing CPU to doing compilation
2.
by boris 1mo ago
> Couldn’t you amortize this to 0 by just caching the result and only changing it if the binary timestamp changed? Yes, that would be nice, but the tricky question is can any of this information change without the compiler binary mtime c
3.
by boris 1mo ago
[build2 author here] Thanks for the feedback! Some additional details: > The first one is a criticism of CMake, not Ninja (?), so I don't think it can be why. Fair enough. The point I was making is that if you want to compete with N
4.
by boris 1mo ago
At least you know it was written by a fallible human. But if you point out my mistake, I will be happy to fix it.
5.
by boris 5mo ago
I don't know, someone who solves their borrow checker errors by adding more dynamic allocations (which seems to be common/recommended), will be taught how to program in Java, not C++.
6.
by boris 5mo ago
> Commands in a CLI … I think what makes for good product design is having a very small number of primitives. Small but not too small. Case in point: shell scripts (POSIX shell, bash) where the scripting part was decided to be modelled a
7.
by boris 9mo ago
GCC (libstdc++) as all other major C++ runtimes (libc++, MSVC) implements the small object optimization for std::function where a small enough callable is stored directly in std::function's state instead of on the heap. Across these im
8.
by boris 9mo ago
The strangest thing about Flow is that its compiler is implemented in C#. So if you decide to use it in your C++ codebase, you now have a C#/.Net dependency, at least at build time.
9.
by boris 10mo ago
I believe the point is if something is UB, like NULL pointer dereference, then the compiler can assume it can't happen and eliminate some other code paths based on that. And that, in turn, could be exploitable.
10.
by boris 11mo ago
What is the filesystem story in OpenBSD? Anything CoW/snapshot'able on the horizon?
11.
by boris 1y ago
What would be the SQLite's equivalent to indexing starting from 1, not 0? Off the top of my head I can't think of anything that would go so much against the grain.
12.
by boris 1y ago
> We have been optimized very hard by evolution to be good at running, so there shouldn’t be any “easy” technologies that would make us dramatically faster or more efficient. I wonder if these new shoes have the same affect on natural (i
13.
by boris 1y ago
There is a parallel with database transactions: it's great if you can do everything in a single database/transaction (atomic monorepo commit). But that only scales so far (on both dimensions: single database and single transaction
14.
by boris 1y ago
Yes, I've seen this one in our logs. Quite obnoxious, but at least it identifies itself as a bot and, at least in our case (cgit host), does not generate much traffic. The bulk of our traffic comes from bots that pretend to be real br
15.
by boris 1y ago
The main reason you would attach a database and then jump through hoops like qualifying tables is to have transactions cover all the attached databases. If you don't need that, then you can just open separate connections to each databa
16.
by boris 1y ago
I would say there is no certainty with eventual consistency, only hope.
17.
by boris 1y ago
> And because Electric syncs every change granularly, you are certain that the state of your local database is exactly the same as the server's. I don't see how this certainty follows from "granularity" (whatever that
18.
by boris 1y ago
> It also has 6 seconds of inactivity before starting any useful work. For comparison, ninja takes 0.4 seconds to start compiling the 2,468,083 line llvm project. Ninja is not a 100% fair comparison to other tools, because it benefits fr
19.
by boris 1y ago
> Header units are supposed to partially address this but right now they are not supported in any build systems properly (except perhaps msbuild?). They are supported in build2 when used with GCC (via the module mapper mechanism it offer
20.
by boris 1y ago
> In other words, hypothetical improvements by AWS (and other Clouds) are extremely overrated. Interesting, in a recent thread (I think it was about Redis going back open source) an AWS employer was bragging about substantial concurrency
21.
by boris 1y ago
I watched that but I don't see it as convincing. Let's take the AWS example brought up in the talk. The "compete on the interface, not (open source) implementation" idea I think misses (at least) the following points: 1.
22.
by boris 1y ago
In our package repository web interface we aimed for high information density over design fluff: https://cppget.org Especially our builds page.
23.
by boris 1y ago
In GCC 14, C++ modules were unusable (incomplete, full of bugs, no std modules, etc). I haven't tried 15 yet but if that changed, then it definitely qualifies for a "great improvement".
24.
by boris 1y ago
Thanks for sharing. If I understood correctly, you have rate-limiter specific urls (those with commit ids) that are infrequently requested by users but frequently by bots. Which means, provided the bots continue trying to request them, any
25.
by boris 1y ago
> How do they know that these are LLM crawlers and not anything else? I can tell you what it looks like in case of a git web interface like cgit: you get a burst of one or two isolated requests from a large number of IPs each for very ob
26.
by boris 2y ago
> and more broadly, there is now a portable, embeddable, and sandboxed version of Perl that others can use in their projects. I can think of a lot of use cases, and helping other developers makes any hardship I endured worth it. Yes, exa
27.
by boris 2y ago
> [M]any developers use C++ as if it was still the previous millennium. [...] C++ now offers modules that deliver proper modularity. C++ may offer modules (in fact, it's been offering them since 2020), however, when it comes to thei
28.
by boris 2y ago
> If make supplied it's own shell language, a simplified one, then everything would be fantastic. We did exactly that in build2, a modern make re-thought. And we provide a bunch of standard utilities like sed, find, etc., that work
29.
by boris 2y ago
> "Processes are the software analog of processors." Yes of course. Maybe this analogy worked in 1986 when hardware was a lot less reliable, but I don't think it goes very far these days: processes die all the time (normal
30.
by boris 2y ago
> Feature Detection Is Better than Version Detection The problem with feature detection (normally referred to as configuration probing), at least the way it's done in ./configure and similar, is that it relies on compiling and

More ›