100 karma · joined February 27, 2025
It's inevitable (no matter how much you enjoy programming) that you will run into frustrating parts of working on code. If at the end of that process, you end up with a product that you know could have been better if LLMs were used, its a shitty feeling and makes it harder to power through the frustrating parts of the work.
There was definitely at least some progress on the problem. I get the general sense that there were potential counterexamples that were close but not quite enough, and that its possible (or even likely) that Claude built on those in order to construct its solution. I also get the sense that when Zhang was working on the problem it was believed that it would be proved true, but since then there were bounds found on the problem that pointed researchers to believe it was false. I am not a research mathematician in this field though, so I could definitely be wrong.
Also, in fairness to Zhang, I believe the dissertation he ended up writing was focused on the 2D case in particular, which is still unsolved (the counter example is only for 3D and above). I cannot imagine that anyone looking at the 2D problem was not also looking at the general case as well though.
> Who says no one was making progress?
Let's look at the Jacobian conjecture, since that was the open math problem I was most familiar with prior to its solution. Yitang Zhang, one of the worlds most renown mathematicians (famous for his lower bound on the twin prime conjecture) spent 8 years working on this problem with his advisor (who himself is a renown mathematician) and turned up completely empty handed. His advisor described it as a "waste [of] 7 years of his own life and my time" [1]. Of course, these two were not the only ones working on this problem for the almost 100 years its been open, but they should have sufficient credentials to show that they were not fools or amateurs.
And in a single afternoon an LLM disproved the conjecture. How is that not an extraordinary feat of technology?
> Who? And doing what?
A close friend is studying differential geometry in a PhD program. Sadly I doubt anything I say on his work will convince you, so I will instead offer two anecdotes:
Terrence Tao (widely considered the worlds greatest living mathematician) has said AI is precipitating "a crisis in the foundations of mathematical values and practices" [2].
Timothy Growers (fields medalist & one of the leading researchers in combinatorics) has said that the latest models are now at the point where they are "producing a piece of PhD-level research in an hour or so, with no serious mathematical input from me" [3].
You can find many more fields medalists and mathematics researchers with the same impression. If you look in this thread you can see bluesky/twitter threads from those who were actively researching some of these problems who are in shock at the solutions.
[1] https://www.math.purdue.edu/~ttm/ZhangYt.pdf [2] https://teorth.github.io/tao-web/slides/age-of-ai-icm-2026.p... [3] https://gowers.wordpress.com/2026/05/08/a-recent-experience-...
Based on [2] a 30B model needs something like 2e+23 FLOPS to train from scratch whereas a 1.6T model needs something like 1e+27 FLOPs to train. So DeepSeek v4 Pro was roughly 5000x more expensive to train than this model. I'm not totally sure how MOE affects scaling laws, so these numbers might be different in reality, but it gives you a good ballpark estimate of the difference in training scale.
[1] https://arxiv.org/abs/2505.12781 [2] https://arxiv.org/abs/2203.15556
C++ offers much higher level primitives out of the box compared to Zig, so I'd say its a higher level language. Of course you can ignore all the features of C++ and just write C, but that's not why people are picking the language.
That being said Rust is definitely a much higher level language than either C or Zig. The availability of `Arc` and `Box`, the existence and reliance on `drop`, and all of `async` are things that just wouldn't exist in Zig and allow Rust programmers to think at higher levels of abstraction when it comes to memory management.
> Having a rich standard library isn't just a pure positive. More code means more maintenance.
I would argue it's much worse to rely on packages that are not in the standard library since its harder to gain trust on maintenance and quality of the code you rely on. I do agree that more code is almost always just more of a burden though.
I am sure you can find truly out-of-distribution cases where the car will make a mistake, but the data shows that this is more rare than a human driver making a mistake.
I am currently working on a fairly involved C & Rust embedded systems project and getting the inter-language interface stable and memory-leak free took a good amount of effort. It probably didn't help that I don't have access to valgrind or gdb on this platform.
1. Is it intending to be a unix-like system?
2. is libc supported? I see that you have XECLib which looks like a custom libc impl?
3. What are the principles behind IPC? I see that there's "PostBox IPC" and that's how windows communicate with the window manager, but from a quick glance I'm not sure how the window manager communicates with the video driver.
4. What's the object format? I see there's docs for XELoader but it doesn't get into how it works or how the linker produces the object files that it loads.
This clearly took a ton of effort and it's a cool project!