aystatic (u/aystatic)

aystatic commented on Welcoming Discord users amidst the challenge of Age Verification matrix.org/blog/2026/02/w... · Posted by u/foresto

oytis · a month ago

This is a wild take. HN has transphobic users like it has trans and ally users. It's neutral to this topic, it's about tech.

aystatic · a month ago

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

aystatic commented on Welcoming Discord users amidst the challenge of Age Verification matrix.org/blog/2026/02/w... · Posted by u/foresto

poly2it · a month ago

Is the implication that HN is transphobic?

aystatic · a month ago

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

aystatic commented on Welcoming Discord users amidst the challenge of Age Verification matrix.org/blog/2026/02/w... · Posted by u/foresto

aystatic · a month ago

you are literally on hackernews

aystatic commented on Same-day upstream Linux support for Snapdragon 8 Elite Gen 5 qualcomm.com/developer/bl... · Posted by u/mfilion

ece · 3 months ago

You would think Apple would update this or put out another support page supporting what you're saying: https://support.apple.com/en-us/102363

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

I think this is more than just an erratum, even with newer chips. It's monopolistic behavior all too common nowadays.

aystatic · 3 months ago

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

aystatic commented on AMD GPU Debugger thegeeko.me/blog/amd-gpu-... · Posted by u/ibobev

shmerl · 3 months ago

tinygrad disagrees.

aystatic · 3 months ago

name 3 things using tinygrad that's not openpilot

aystatic commented on Same-day upstream Linux support for Snapdragon 8 Elite Gen 5 qualcomm.com/developer/bl... · Posted by u/mfilion

ece · 3 months ago

This comparison makes no sense. It's desktops/laptops vs phones. In either case Apple is the worst offender. You cannot even use Nvidia/AMD/Intel DGPUs with AS Macs, or install other OSes on iPhone.

aystatic · 3 months ago

> 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

aystatic commented on A million ways to die from a data race in Go gaultier.github.io/blog/a... · Posted by u/ingve

lenkite · 4 months ago

I did say "runtime borrow checking" ie using them together. Example: `Rc::new(RefCell::new(value));`. This will panic at runtime. Maybe I should have used the phrase "dynamic borrowing" ?

https://play.rust-lang.org/?version=stable&mode=debug&editio...

You don't need different threads. I said concurrency not multi-threading. Interleaving tasks within the same thread (in an event loop for example) can cause panics.

aystatic · 4 months ago

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...

aystatic commented on A million ways to die from a data race in Go gaultier.github.io/blog/a... · Posted by u/ingve

lenkite · 4 months ago

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

Anyways, the article author lacks basic reading skills, since he forgot to mention that the Go http doc states that only the http client transport is safe for concurrent modification. There is no "subtlety" about it. It directly says so. Concurrent "use" is not Concurrent "modification" in Go. The Go stdlib doc uses this consistently everywhere.

aystatic · 4 months ago

> Runtime borrow checking: RefCell<T> and Rc<T>. 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)

aystatic commented on There is no memory safety without thread safety ralfj.de/blog/2025/07/24/... · Posted by u/tavianator

pclmulqdq · 8 months ago

A not-so-secret secret of Rust is that liberal use of 'unsafe' is pretty much required for certain classes of high-performance code.

aystatic · 8 months ago

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

aystatic commented on Show HN: Lstr – A modern, interactive tree command written in Rust github.com/bgreenwell/lst... · Posted by u/w108bmg

ethan_smith · 9 months ago

Try `cargo build --release --no-default-features` to get a much smaller binary (~5-10MB) - Rust statically links dependencies but supports conditional compilation for optional features.

aystatic · 9 months ago

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

u/aystatic

KarmaCake day27December 27, 2023View Original