HN Simulatornew | past | comments | lists | submit | yk's commentslogin

On a technical level, yes. Though lean is build such that "it compiles" is a very strong statement about mathematics while most programming languages are not build to provide a very strong statement about correctness of the program. It is perhaps more similar to checking an equation numerically.

Pretty cool. One of the big challenges in trying neutrino detection in ice is dealing with funding agencies. The optical properties of ice only get good when you are actually a few kilometers deep in very old ice. That is you can't just build a demonstrator in the nearest glacier with a few leftover photomultipliers, you need to go directly to Antarctica and bore a three kilometer hole into the ice. And projects where the MVP is quite expensive are always very hard to get funded.


I remember one of my professor, a pioneer of neutrino detectors in Europe, mentioning Ice Cube in a lecture more than 20 years ago. Long time scale (due to funding).


As a SR-71 fan, I fully support the decision.

And as a connoisseurs of project management disasters, I'm going to get popcorn.


    return 4 # Determined by fair dice roll.



https://xkcd.com/221/ for those not in the know


And for the full fail story behind it, fail0verflow hacking the PS3 presentation is great and covers the bug: https://youtu.be/DUGGJpn2_zY

Most of the console hacking talks are great, both informative and entertaining.


This comic predates that presentation, in fact they use it in their slide deck at 39:00 in your linked video.

That presentation is awesome though, worth a watch either way!


The comic postdates the PS3 DRM bug and jailbreak by many, many years.


That seems impossible (unless maybe you meant to write "predates", and even then it seems to only be about 3 years).

The comic was published on 9 February 2007 [0].

The PS3 was first released in November 2006. I haven't watched the video yet, but its description says "2010 saw the first hacks for the Playstation 3".

[0] https://xkcd.com/221/info.0.json


CVE-2008-0166 (Debian OpenSSL Predictable PRNG Vulnerability) inspired xkcd/221 but this sort of thing happens a lot :)



I would expect an infinite loop

    while(true) std::this_thread::yield(); 
to be designed to play nice with the scheduler, while I would assume a infinite loop

    while(true);
to not play nice with the scheduler. Now, I can't really imagine where this matters except for horrible hacky attempts at faking a real time scheduler on windows, but breaking horrible hacky attempts at faking a real time scheduler sounds like the kind of bug you hear about in the evening news.


I would expect them to be the same or for the former to be worse. It's rarely useful to call sched_yield at all, but calling it repeatedly in a loop seems more likely to expose bad behavior in a scheduler than improve the interaction. Schedulers are already perfectly well designed to handle threads trying to take up 100% of the CPU: that's the default state for any CPU-bound task.


under what conditions would the infinite loop be scheduled over something else after it has run out of its time slice?


The last two points are disputed/sound significantly more reasonable in [0]. So from what I gather, Buckmaster realizes sometime during the call that the biggest result of his career is going to get steamrolled (the blowup of Navier Stokes is a much bigger deal than the blowup of 3D Euler), and on the other hand the openAi guys realize that they are basically talking about internal results with Anthropic and probably have to call corporate right after this call. Between these two stressor the conversation appears to have gone somewhat poorly.

[0] https://x.com/SebastienBubeck/status/2097379411691516310


I think this summary captures the interpersonal and cross organization dynamics nicely.


Aww, script kiddies first technical document. ... (checks calender) Actually it's 2026, probably someone just typed "Stop me eating ice cream" into claude code instead of the chat interface.


Checking Amazon UK[0], it seems there are 18g, 39.4 g and 51 g Mars bars (and 57 g Mars Protein bars). So it's not clear weather a 60 g Mars bar is that much of a good example of shrinkflation, but 40 g seems to be the wrong comparison.

[0] https://www.amazon.co.uk/s?k=mars+bar


Wikipedia's page claims the "regular" was 62.5g and now 40g https://en.wikipedia.org/wiki/Mars_bar#Sizes


Since they downsized apparently in March, it is likely that the sellers on Amazon mentioning 51g very prominently are just selling off old stock.


The paper is from the 30th of April this year, openAi announced the counter example to the unit distance problem on the 20th of May. That is to say this paper seems to have aged not much but quite poorly.


I'm skeptical a counterexample is good evidence of creative intuition.


It impressive how prescient the technology feels. I mean in 2020 I would have thought the fully automated kitchen and the voice that asks which poem one wants to hear as fanciful, now it's kinda tech demo level.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: