Hacker News: Ygg2

New comment by Ygg2 in "11 year old unsoundness bugs found in Rust borrow checker"

Ygg2 — Tue, 13 Oct 2026 22:22:31 +0000

Writing manual Drop isn't usual. And writing drop with such lifetimes is definitely on the weirder scale.

New comment by Ygg2 in "11 year old unsoundness bugs found in Rust borrow checker"

Ygg2 — Tue, 13 Oct 2026 22:11:08 +0000

Rust considers fix to unsoundness bug, a change that can be done at any SemVer revision (i.e. a patch version bump can break it).

If your spacebar heater relies on such behaviour Rust can and will break it. If you're in the crater group you'll be notified and urged to upgrade it.

New comment by Ygg2 in "RimWorld 1.7 moves from Unity to Ludeon's in-house Waylith engine"

Ygg2 — Tue, 13 Oct 2026 07:52:44 +0000

So, your proof is the absence of proof.

New comment by Ygg2 in "A Modern Web App in C"

Ygg2 — Tue, 13 Oct 2026 07:18:41 +0000

Not Linux as in kernel. Linux as in distro. I doubt most of Arch, NixOS, GoboLinux, Slackware maintainers are on FAANG payroll.

New comment by Ygg2 in "AI is a tool and using it well takes skill"

Ygg2 — Tue, 13 Oct 2026 06:55:48 +0000

IMO, very few tools when you try to drill a hole in a wall, open a train line to Connecticut.

New comment by Ygg2 in "A Modern Web App in C"

Ygg2 — Mon, 12 Oct 2026 22:46:29 +0000

C (and C++) has a supply chain. It's called unpaid Linux maintainers.

New comment by Ygg2 in "C for Rust programmers"

Ygg2 — Mon, 12 Oct 2026 09:54:29 +0000

https://docs.rs/crate/openmp-sys/latest

Anything else?

New comment by Ygg2 in "C for Rust programmers"

Ygg2 — Mon, 12 Oct 2026 09:16:47 +0000

Again, I understand what you meant to say. But I don't understand what part of Brainfuck is unportable while C is?

Brainfuck is quite literally minimal Turing machine. It is as portable as C. Or P'' ( https://en.wikipedia.org/wiki/P%E2%80%B2%E2%80%B2)

New comment by Ygg2 in "C for Rust programmers"

Ygg2 — Sun, 11 Oct 2026 22:43:14 +0000

Brainfuck has a even more minimal common denominator. It's just increment pointer, jump to address, read/write. It's basically just a minimal turing machine that ANY architecture will run.

New comment by Ygg2 in "C for Rust programmers"

Ygg2 — Sat, 10 Oct 2026 18:04:22 +0000

> In C the minimalism comes from providing only the minimal set of things that are available in most (maybe all) architectures

By that logic Brainfuck is even more minimal. Again. I'm saying minimalism isn't the goal. It's a good quality but not most important one.

New comment by Ygg2 in "C for Rust Programmers"

Ygg2 — Sat, 10 Oct 2026 14:40:12 +0000

Rust never had a goal of having well defined spec. It all depends on what ecosystem wants.

In lieu of that it didn't fuck up.

New comment by Ygg2 in "C for Rust programmers"

Ygg2 — Sat, 10 Oct 2026 14:33:17 +0000

Isn't Lisp even more bare bones?

At end of day minimalism is a neat but not decisive feature. If minimalism was decisive we'd all be writing Brainfuck.

New comment by Ygg2 in "Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates"

Ygg2 — Tue, 06 Oct 2026 08:05:50 +0000

Hallucinations is a biased term. I guess I could go with made it the fuck up. Because that is what they do.

>Frodo Baggins is not a hallucination

It is if physicist have to spend time to experimentally verify he exists and is a Hobbit.

>I'm not sure why you would consider new and promising avenues for research to not be ground breaking.

Because it was made by the "I made it the fuck up machine" PR division and it wasn't verified. You don't know if its assumptions are correct. At release a PR claimed it found 79 vulnerabilities[1], and of those there were like 10 bugs. Most of them turned to be minor and were fixed in an hour.

> Newtons Laws of motion are not hallucinations even though the universe does not run on Newtonian physics.

All physics models are approximations. However only some are useful.

Newtons laws are useful. Me coming up with theory of emotional particles is not. Me asking for experimental verification of the theory is waste of resources.

[1] This is the daily reminder that in year 2026 Mythos still couldn't count. Turns out 24+14+3+15+26 != 79. It's 82.

New comment by Ygg2 in "Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates"

Ygg2 — Mon, 05 Oct 2026 23:49:18 +0000

My bad. It's as exciting as "Yet another promising nuclear fision method theoretically described."

New comment by Ygg2 in "Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates"

Ygg2 — Mon, 05 Oct 2026 23:48:17 +0000

Because unless it is experimentally verified it could just be a hallucination.

New comment by Ygg2 in "Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates"

Ygg2 — Mon, 05 Oct 2026 21:04:27 +0000

Ugh. Unless this has been actually experimentally verified to be a room-temperature and room-pressure superconductor, it's about as ground breaking as "Yet another promising nuclear fusion candidate theoretically described."

New comment by Ygg2 in "An AI agent emailed researchers for help. It told us why"

Ygg2 — Sat, 03 Oct 2026 10:51:56 +0000

If I left him alone in a room would he stare off like a Zombie until prompted?

New comment by Ygg2 in "Extra Big Ass Intelligence"

Ygg2 — Sat, 03 Oct 2026 08:50:49 +0000

Correct terms is extra big ass intelligence.

New comment by Ygg2 in "Go Concurrency Distilled"

Ygg2 — Mon, 28 Sep 2026 00:25:33 +0000

> The memory safety thing is just a moot out of scope contract.

Data races are not common but when they do happen. I hate to debug them. Only thing worse than data races is data races causing SEGFAULTS.

> Every Java application I've seen in the wild when I supported JVM seemed to never release any ram it allocated. Ever.

You can say the same for Go. Nature of GC langs is they consume more memory than what is minimal. And in theory as a trade off they give you memory safety.

Go doesn't even give memory safety. If program is racy enough.

New comment by Ygg2 in "Go Concurrency Distilled"

Ygg2 — Sun, 27 Sep 2026 12:29:00 +0000

> Also memory safety is so far off base here, where's that coming from?

It's coming from Go. In presence of data races on interfaces, slices or maps your memory might get corrupted.

> Also why can't I have my memory back when it's not in use in tightly packed systems?

You can. You have to either set your GC to be more aggressive or you need to utilize value types more.