Hacker News: aystatic

New comment by aystatic in "Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc"

aystatic — Sat, 09 May 2026 20:17:34 +0000

That's a hell of a lot more than "basic extrapolation." You're misrepresenting the original claim to fight against one that's trivially easy to dispute. "Bun has had an extremely high amount of crashes/memory bugs due to them using Zig" (which unlike Rust, doesn't prevent you from writing them) is a completely different statement than your "using Zig results in an extremely high amount of crashes/bugs." Implying that such a generalization was even on the table is insulting.

Yes, obviously you can write high-quality software in Zig. But does Zig categorically reject the kind of bugs Bun was suffering from? Rust does.

New comment by aystatic in "Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc"

aystatic — Sat, 09 May 2026 19:21:42 +0000

> Is your claim that using Zig ends in an "extremely high amount of crashes/memory bugs?" Wouldn't that mean that it isn't even feasible to make high-quality software with such a tool?

What caused you to hallucinate such a broad blanket statement? The point is the memory unsafety issues they ran into would be categorically impossible in safe Rust, which is why they're doing this in the first place.

New comment by aystatic in "Welcoming Discord users amidst the challenge of Age Verification"

aystatic — Thu, 12 Feb 2026 21:59:44 +0000

i don't think it's that "wild". sure, i'm not so cynical as to feel hn's become a nazi bar or anything, but i am willing to recognize that some of the incidents i've witnessed could be reason enough for a trans person to want to avoid this site.

> It's neutral to this topic, it's about tech.

this thread began by xe bringing up failures in moderation affecting trans people

New comment by aystatic in "Welcoming Discord users amidst the challenge of Age Verification"

aystatic — Thu, 12 Feb 2026 21:31:04 +0000

you're free to have your own opinion based on your experiences here, but i wouldn't blame anyone for feeling that way. for the record, i don't think dang or anybody is a transphobe, but i have to imagine the culture here is pretty off-putting to trans people

https://news.ycombinator.com/item?id=36231993

New comment by aystatic in "Welcoming Discord users amidst the challenge of Age Verification"

aystatic — Thu, 12 Feb 2026 21:23:20 +0000

you are literally on hackernews

New comment by aystatic in "Same-day upstream Linux support for Snapdragon 8 Elite Gen 5"

aystatic — Tue, 09 Dec 2025 21:57:54 +0000

don't see why they would care to put out docs on it considering macos doesn't even permit kexts anymore, there'd be no gpu drivers anyways. i figured it was obvious we're talking in the context of running linux on these things, given the parent topic.

> There's also an Apple VP saying unified memory on AS doesn't leave room for DGPUs and separate VRAM

can you link to this? my intuition is that they're speaking on whether apple would include dgpus inside AS systems like they used to with nvidia and amd chips in macbooks, which i agree wouldn't make much sense atp

New comment by aystatic in "AMD GPU Debugger"

aystatic — Tue, 09 Dec 2025 00:40:48 +0000

name 3 things using tinygrad that's not openpilot

New comment by aystatic in "Same-day upstream Linux support for Snapdragon 8 Elite Gen 5"

aystatic — Tue, 09 Dec 2025 00:16:39 +0000

> You cannot even use Nvidia/AMD/Intel DGPUs with AS Macs

afaik you technically can, except that m1/m2 force pcie bars to be mapped as device memory (forbids unaligned r/w), so most gpu software (and drivers) that just issue memcpys to vram and expect the fabric to behave sanely will sigbus. it's possible to work around this, and some people indeed have with amdgpu, but it'd absolutely destroy performance to fix in the general case

so it doesn't really have anything to do with apple themselves blocking it but rather a niche implementation detail of the AS platform that's essentially an erratum

New comment by aystatic in "A million ways to die from a data race in Go"

aystatic — Tue, 25 Nov 2025 18:38:41 +0000

I understand what you meant (but note that allocating an Rc isn’t necessary; &RefCell would work just fine). I just didn’t see the “subtle linguistic distinctions” - and still don’t… maybe you could point them out for me?

https://doc.rust-lang.org/stable/std/cell/struct.RefCell.htm...

New comment by aystatic in "A million ways to die from a data race in Go"

aystatic — Tue, 25 Nov 2025 16:21:17 +0000

> Runtime borrow checking: RefCell and Rc. Can give other examples, but admittedly they need `unsafe` blocks.

Where are the “subtle linguistic distinctions”? These types do two completely different things. And neither are even capable of being used in a multithreaded context due to `!Sync` (and `!Send` for Rc and refguards)

New comment by aystatic in "There is no memory safety without thread safety"

aystatic — Fri, 25 Jul 2025 19:21:30 +0000

imo if you're sprinkling around `unsafe` in your codebase "liberally", you're holding it wrong. In general it's really not that hard to encapsulate most unsafety into a wide-contract abstraction; I’d argue where Rust really shines is when you take advantage of the type system and static analyzer to automatically uphold invariants for you

New comment by aystatic in "Show HN: Lstr – A modern, interactive tree command written in Rust"

aystatic — Wed, 18 Jun 2025 03:04:23 +0000

Glancing at the Cargo.toml, the package doesn't define any features anyways. `cargo b --no-default-features` only applies to the packages you're building, not their dependencies -- that would lead to very unpredictable behavior

New comment by aystatic in "Show HN: Lstr – A modern, interactive tree command written in Rust"

aystatic — Wed, 18 Jun 2025 02:20:16 +0000

Neat, looks like a combination of erdtree[0] and broot[1]. I use both on a daily basis, are there any features that stand out from the two?

[0]: https://github.com/solidiquis/erdtree [1]: https://github.com/Canop/broot

New comment by aystatic in "(On | No) Syntactic Support for Error Handling"

aystatic — Tue, 03 Jun 2025 18:28:29 +0000

You've managed to miss the entire point of using a union: the value is either a success payload or an error value, never both.

You can't encode that mutual exclusivity if you return a std::pair or std::tuple. That's exactly why std::expected, std::variant, or Rust enums exist, to make that constraint explicit in the type system.

New comment by aystatic in "(On | No) Syntactic Support for Error Handling"

aystatic — Tue, 03 Jun 2025 17:01:30 +0000

I don't know that there's whining about "having to handle errors" in principle, it's pretty clearly a complaint with the syntax and semantics of doing so

Some languages even make omitting error handling impossible! (e.g. Result sum types). None have anywhere near the amount of "whining" Go seems to attract

New comment by aystatic in "Launch HN: Relace (YC W23) – Models for fast and reliable codegen"

aystatic — Wed, 28 May 2025 01:52:46 +0000

Codex-like agents are cool but as someone with even just a passing interest in compilers I absolutely hate this attempt at appropriating the word "codegen"

New comment by aystatic in "Migrating away from Rust"

aystatic — Tue, 29 Apr 2025 01:50:44 +0000

?? the whole point of Box is to be an owning reference, you can’t have multiple children refer to the same parent object if you use a Box

New comment by aystatic in "Go's Error Handling Is Perfect"

aystatic — Fri, 05 Apr 2024 15:44:18 +0000

I don't necessarily disagree with the overall point, but I'm sad the article misses the big advantage to the sum-type solution. It is not just about "being able to collapse `res, err := func()` into `res := func()?`". With sum types you literally cannot access the Result's inner value without performing some kind of error handling. Even if you just `.unwrap()`.

from https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-...

> The point is, this function signature makes it impossible for us to access an invalid/uninitialized/null Metadata. With a Go function, if you ignore the returned error, you still get the result - most probably a null pointer.

New comment by aystatic in "DeskHop – Fast Desktop Switching"

aystatic — Wed, 27 Dec 2023 15:00:12 +0000

This announcement was only added to the README in early October[1]. In the meantime you can of course compile it yourself/grab a build from GH actions. I'm sure they would appreciate the testing, especially leading up to release :-)

[1]: https://github.com/input-leap/input-leap/commit/78ca8f1ef7b6...