omcnoe

6 ms·

31.
by omcnoe 6mo ago
I think it also represents a bet that in some sense Cursor's model capabilities are resource limited rather than talent limited. If that's true, $60B will end up being a bargain. If not true, well it's an expensive lesson but
32.
by omcnoe 6mo ago
Problem is basically, that if the option works out (Cursor truly has the talent to train a frontier model on SpaceX's infrastructure, and were simply lacking the infra before) the fair price would be way way more than $60B. OpenAI trie
33.
by omcnoe 6mo ago
It's true that Cursor doesn't have their own frontier models, but they are training their own models. They just aren't at frontier level yet. The $60B/$10B deal looks like a bet that this is a capital/GPU constrai
34.
by omcnoe 6mo ago
The problem is, the ways that it's great are hard to put into words and explain for someone unfamiliar with the game. At least, not in a succinct way. At the most basic level it's just block pushing puzzles ("Sokoban").
35.
by omcnoe 6mo ago
Trying to copy is a bit harsh, but he has credited it as an inspiration for what's possible within the Sokoban format. I believe he was a playtester for SSR before it released, mid The Witness development.
36.
by omcnoe 6mo ago
If you can correctly add all the required explicit bounds checks in C what do you need Fil-C for?
37.
by omcnoe 6mo ago
It's an apple to non-existent-apple comparison. Fil-C can't handle it even with extra code because Fil-C provides no recovery mechanism. I also don't think it's that niche a use case. It's one encountered by every w
38.
by omcnoe 6mo ago
Not trying to be a Rust advocate and I actually don't work in it personally. But Rust provides both checked alternatives to indexed reads/writes (compile time safe returning Option<_>), and an exception recovery mechanism fo
39.
by omcnoe 6mo ago
https://play.rust-lang.org/?version=stable&mode=debug&editio... Catch the panic & unwind, safe program execution continues. Fundamentally impossible in Fil-C.
40.
by omcnoe 6mo ago
I don't think that's a useful way of thinking about memory-safety - a C compiler that compiles any C program to `main { exit(-1); }` is completely memory-safe. It's easy to design a memory-safe language/compiler, the que
41.
by omcnoe 6mo ago
The issue with Fil-C is that it's runtime memory safety. You can still write memory-unsafe code, just now it is guaranteed to crash rather than being a potential vulnerability. Guaranteed memory safety at compile time is clearly the be
42.
by omcnoe 6mo ago
I am writing a whitespace sensitive parser - trimming whitespace matters because whitespace consumption is used to implement the indentation rules/constraints. For example, doing things like passing an indentation sensitive whitespace
43.
by omcnoe 6mo ago
Been working on a toy compiler for fun recently. I have ignored all the stuff about parsing theory, parser generators, custom DSL's, formal grammers etc. and instead have just been using the wonderful Megaparsec parser combinator libra
44.
by omcnoe 6mo ago
This is a hilarious, and also terrible, reason. Why can't we let the FIPS people play in their own weird corner, while not compromising whole internet security for their sake? OpenSSL is too important to get distracted by a weird US-sp
45.
by omcnoe 6mo ago
No, only if your website abuses window.history.pushState to redirect the user to spam/ad content is it considered abuse.
46.
by omcnoe 6mo ago
There are subtle gotchas around sequential UUID compared to serial depending on where you generate the UUIDs. You can kinda only get hard sequential guarantee if you are generating them at write time on DB host itself. But, for both Serial
47.
by omcnoe 6mo ago
DB perf considerations aside, a lot of software pattern around idempotency/safe retries/horiz-scaling/distributed systems are super awkward with a serial pk because you don’t have any kind of unambiguous unique record identif
48.
by omcnoe 6mo ago
It also contains a wonderfully prescient question asked right at the end of the talk: "... the processor gonna speculate, doing some loads out of the bounds of the array, how does it work in the hardware that it doesn't crash?&quo
49.
by omcnoe 6mo ago
Difference is the scaffold isn’t “loop over every file” - it’s loop over every discovered vulnerable code snippet. If you isolate the codebase just the specific known vulnerable code up front it isn’t surprising the vulnerabilities are easy
50.
by omcnoe 6mo ago
The methodology here is completely wrong, outright dishonest. Finding a needle in a haystack is easy if someone hands you the small handful of hay containing the needle up front, and raises their eyebrows at you saying “there might be a nee
51.
by omcnoe 6mo ago
I think you have it swapped around. This is exactly the kind of workflow that git provided better support for - lightweight branches, not integral part of master history, deleted after merge.
52.
by omcnoe 6mo ago
Is it actually redacted, or just a leftover stub from a feature implemented in silicon instead of software? Isn't the x86 memory order compatibility done at hardware level?
53.
by omcnoe 6mo ago
Lightweight branch model of git mapped so much better to the way that actual development processes of medium to large projects really work(ed). Named branches vs bookmarks in hg just means bike shedding about branching strategy. Bookmarks u
54.
by omcnoe 6mo ago
ARM macs apparently have some kind of specific handling in place for this when a process is running with x86_64 compatibility, but it’s not publicly documented anywhere that I can see.
55.
by omcnoe 6mo ago
But, we are also starting to think about putting security barriers in front of that architecture like W^X.
56.
by omcnoe 6mo ago
There are so many reasons why C/C++ build systems struggle, but imo power is the last of them. "Powerful" and "scriptable" build systems are what has gotten us into the swamp! * Standards committee is allergic to st
57.
by omcnoe 6mo ago
Yes - eg. page 192 BrowseComp bunchmark. Mythos preview has higher accuracy with fewer tokens used than any previous Claude model. Though, the fact that this incredibly strong result was only presented for BrowseComp (a kind of weird benchm
58.
by omcnoe 6mo ago
It’s a paper gain created by mark to book accounting treatment of central bank goal reserves. Not a real economic gain. The US could re-create the same “gain” by selling and repurchasing their gold. Fundamentally doesn’t really matter.
59.
by omcnoe 6mo ago
Mark to market versus mark to book accounting for central bank gold reserves is an endless source of crank adjacent debates.
60.
by omcnoe 6mo ago
Every suggestion when encountering a Windows OS bug is "run sfc /scannow" - has this ever solved a problem for anyone?

More ›