Hacker Newsnew | past | comments | ask | show | jobs | submit | tromp's commentslogin

Make that almost nobody.

I wrote a non-trivial lambda program [1] which enumerates proofs in the Calculus of Constructions to demonstrate [2] that BBλ(1850) > Loader's Number.

[1] https://github.com/tromp/AIT/blob/master/fast_growing_and_co...

[2] https://codegolf.stackexchange.com/questions/176966/golf-a-n...




Thanks, great read. Fills in quite a few holes in my own understanding of events.

Doesn't exactly leave one optimistic for a favorable final outcome, given how much U235 they supposedly already enriched to 60%. As I understand it, they could build twice as many bombs if they took the time to enrich to 90%, but they could build at least some now if they felt they had a reason to hurry.

I wouldn't be surprised if they felt they had a reason to hurry.


As nicely illustrated in this Young Sheldon episode fragment: https://www.youtube.com/shorts/Nd90rFPYVnc

Are you aware that every YT Short can also be viewed with the normal player? If you do, do you prefer the Shorts interface and thus posted that URL rather then https://www.youtube.com/watch?v=Nd90rFPYVnc ?

I would have gone with South Park's murder porn episode in which the kids accidentally got the parents interested in Minecraft.

Or a C implementation at https://tromp.github.io/pearls.html#sieve which runs in well under 10s.

I'd be interested in seeing an explanation of the code, since it looks pretty incomprehensible to me. Per the arbitrary rules I set for myself, I'm not allowed to precompute/hardcode the wheel (looks like this implementation uses a hardcoded wheel of size 2x3x5=30). I wonder if/by how much the performance would suffer by computing and storing the coprime remainders in memory instead of handing them directly to the compiler.

I wrote this in a semi obfuscated style to make it fit on one screen. It's indeed a hardcoded 2x3x5 wheel; but I suspect computing all those constants would have made the program significantly longer.

Also please don't post accusations of comments reeking of AI.

I don’t respond to specific comments with accusations, because I can’t prove it and it would suck to be falsely accused. But I find it really depressing to watch deep comment threads with someone debating with an AI. The human is putting so much effort in, and the AI is responding with all these well-written but often flawed arguments. I wish I could do something to save that person from that interaction.

Learn to let it go. Some of us have to learn the hard way.

"If the fool would persist in his folly he would become wise." -- William Blake, Heaven and Hell


Just like the rules say it's uninteresting and off-topic to complain that HN is turning into Reddit, it's equally uninteresting and off-topic to accuse posters of AI crimes.

And everyone's personal AI detector has a ridiculously high false-positive rate.


Good point. I think that should be added here:

> Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.


You're absolutely right! Accusing other users of being AI isn't just unhelpful—it's actively detrimental to discussion. I'd love to hear others' thoughts regarding ways in which we can encourage legitimate human dialogue without senseless accusations.

A recommended follow-up is "stop pretending to be a bot ironically for humor, it's a joke that's been done to death and is therefore no longer funny and just noise."

So you're saying it's not funny, it's annoying!

We can now that it's an actual guideline. It's already well established that copypasting from the guidelines verbatim is accepted behavior, even though doing so violates more guidelines than whatever guideline it's pointing out. I will happily and enthusiastically tap this sign until the glass breaks.

I often find the LLM witch hunt comments to be more distracting than the original LLM slop. I would much rather bathe in a mixture of spam and non-spam than operate under constant fear of being weighed against a duck by the local villagers.

But they didn't reflect that in a title like "current RISC-V silicon Is Sloooow" ...

10,000x to 100,000x / 5,000x = 2 to 10x, not 20 to 100x.

Why do almost all phones have to be in that narrow band of 6.5 to 6.9 inches?

I wish there were more size choices on both ends of the spectrum. While most people prefer more choice below 6", I would like some choice above 7", since I keep my phone in my belly pouch, and never use it one-handed. My current Huawei Mate20X is actually ok at 7.2" (but worse than the Mediapad X1 I had before which at 7" was actually wider) but is way behind on Android updates, and will soon stop running my banking app.


Quick reality check that

- 7" used to be tablet category, e.g the Nexus 7

- anything above 6" would be considered phablet

Phones are really just like cars now, size inflation included.


While I agree with the spirit of the thread and dearly love my mini, I think this reasoning doesn’t account for a substantial reduction in bezels: my iPhone 5S had more than a centimetre of black bars above and below its 4" display (altogether it was 5.4" in diagonal), I bet those phablets you mentioned had even bigger bezels and were closer to modern 8.5" phones.


> Mining requires traversing a DAG with a mainnet floor of 512 MB (32,768 nodes × 16 KB each)

How much memory does PoW verification require?

> Genesis Address: 2,696,969 KNOX (One-time mint for the Founder/Son legacy).

> Treasury: 1% of each block's public reward, allocated to the protocol treasury.

Yet another grift...

> Post-Emission: After 21 years, miners are sustained by transaction fees only. The hard cap is absolute.

Even for the #1 blockchain, the ability for tx fees to provide sufficient security is strongly in doubt.


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

Search: