mbrock

4 ms·

1.
by mbrock 1mo ago
yes I use that exact feature constantly to use Codex on remote servers and it works great
2.
by mbrock 2mo ago
In the ISO standard, yeah, but that's not how C actually works.
3.
by mbrock 2mo ago
It would work basically the way it works on Linux? What makes you think it's somehow fundamentally Linux-specific?
4.
by mbrock 2mo ago
Not really. I mean if you want to make that claim, use actual quotes.
5.
by mbrock 2mo ago
Fil-C's understanding of memory safety is not "its own" idiosyncratic made up definition. Memory safety in the whole tradition that includes CHERI etc is defined in terms of objects and allocations. In C structs and arrays ar
6.
by mbrock 2mo ago
> Fil-C is the worst of all worlds here. Like C, it forces you to manually manage your own memory. Can you expand on this?
7.
by mbrock 2mo ago
There is an unsafe call primitive in stdfil that was used to support constant time crypto functions when Fil-C didn't have support for inline assembly. Fil-C now has support for inline assembly, so it's not needed anymore, and I b
8.
by mbrock 2mo ago
> I do not go around posting "omg Rust is SO MUCH BETTER than zig or fil-c, which are TRASH." I talk about engineering tradeoffs, and what matters to me personally. I do not say "if you use Zig, you are a bad person.&quot
9.
by mbrock 2mo ago
The same basically holds for proofs in the absence of coherent global correctness criteria like, say, confluence and normalization for a lambda calculus, or soundness and completeness for a logic. Fable's napkin estimate of the effort
10.
by mbrock 4mo ago
Faster in what browser, by what measure, for what modules? "X is faster than Y" without any concretization is usually meaningless.
11.
by mbrock 4mo ago
You can do something like (y > 0 && x > INT_MAX - y) || (y < 0 && x < INT_MIN - y) and hope the optimizer turns it back into just checking the result. Or you use -fwrapv to concretize the ISO amb
12.
by mbrock 4mo ago
okey dokey
13.
by mbrock 4mo ago
Well yeah that just means some aspects of the imaginary compiler were in some configurations approximated by some historical compiler versions and were in some cases rejected by the community (which cares about sane semantics even for behav
14.
by mbrock 4mo ago
you mean removing the JIT?
15.
by mbrock 4mo ago
ok what's the alternative?
16.
by mbrock 4mo ago
yeah then I have to learn how it works and what it assumes and how I can control it and maybe switch to a more well behaved compiler if it's truly insane
17.
by mbrock 4mo ago
Right, good example, and both GCC and Clang offer well understood parameters for deciding, per compilation unit, what behavior you want for signed overflow (-fwrapv, -fno-strict-overflow, etc), so in reality it's quite far from spooky
18.
by mbrock 4mo ago
Yet the standard does not tell you what the compilers do. Linux works on a wide variety of platforms. It also relies on those platforms behaving predictably with respect to what the standard leaves undefined. This description of ISO UB as a
19.
by mbrock 4mo ago
This is a description of an imaginary compiler, evoked by the ANSI/ISO standards documents, which has never existed and will never exist. To understand what the program will do, you just have to understand the compiler behavior on your
20.
by mbrock 4mo ago
undefined behavior is the behavior of code patterns "for which this International Standard imposes no requirements" and the behavior is in fact almost always predictable and agreed upon by compiler vendors and the users of the lan
21.
by mbrock 4mo ago
most languages don't even HAVE a specification so in most languages literally EVERYTHING everything is undefined behavior
22.
by mbrock 7mo ago
If you stop trying to find something like truly ontologically novel about it, you might be able to understand what it actually is. Okay it's not impressive. It's not incredible. It's not groundbreaking new technology. It is w
23.
by mbrock 8mo ago
That kind of blanket demand doesn't persuade anyone and doesn't solve any problem. Even if you get people to sit and press a button every time the agent wants to do anything, you're not getting the actual alertness and rigor
24.
by mbrock 9mo ago
Flexner's "Understanding Wood Finishing" has a section about "the myth of food safety" that pretty directly states that food safety isn't a serious concern for fully cured finishes.
25.
by mbrock 9mo ago
The solvents evaporate when the lacquer cures, right? A lacquered spatula or spoon could leach some plasticizers when heated up. But who on earth would go to the trouble of spray lacquering a spatula? It doesn't seem like a real concer
26.
by mbrock 9mo ago
The author seems to have forgotten to mention WHY he wants scrapers to use APIs instead of HTML.
27.
by mbrock 9mo ago
I think all wood finishes are "food safe" once they're cured.
28.
by mbrock 9mo ago
Great! Feel free to ask questions or report problems on GitHub or the Fil-C Discord. If some package doesn't compile I can probably look into it!
29.
by mbrock 9mo ago
FYI nginx and Apache and Postgres using shared memory across processes make them hard to use with Fil-C. Lighttpd works well though!
30.
by mbrock 9mo ago
If you're into Nix, check out https://github.com/mbrock/filnix — not yet integrated & maintained in upstream Nixpkgs, but lets you replace Nix/NixOS packages with Fil-C versions quite easily.

More ›