throwaway38294 (u/throwaway38294)

throwaway38294 commented on FBI raids Washington Post reporter's home theguardian.com/us-news/2... · Posted by u/echelon_musk

andsoitis · 2 months ago

> And there has been plenty US citizens deported under DHS.

Are you sure? Do you mind linking to information / reporting about that? I have not seen any.

throwaway38294 · 2 months ago

How about starting on the wikipedia page:

https://en.wikipedia.org/wiki/Deaths,_detentions_and_deporta...

Then you can read the congressional report:

https://www.congress.gov/119/meeting/house/118180/documents/...

At this point this is not an accident it's an intentional policy to spread fear and suppress dissent

throwaway38294 commented on The chess bot on Delta Air Lines will destroy you (2024) [video] youtube.com/watch?v=c0mLh... · Posted by u/cjaackie

teraflop · 2 months ago

I guess it's just a display bug, then? Though it's hard to imagine what kind of bug would lead the game state and the visual representation to get out of sync in that particular way.

throwaway38294 · 2 months ago

My guess is they only remove captured pieces on the moved-to square (maybe relying on an implicit capture by overwriting an array entry). This is probably easier than actually tracking pieces that get captured.

throwaway38294 commented on Time-Traveling to 1979: Advice for Designing 'C with Classes coderschmoder.com/i-time-... · Posted by u/birdculture

throwaway38294 · 3 months ago

It's super weird to say that we need rvalue references. rvalues with their odd semantics are only needed so that they don't break compatibility with the current reference/temporary rules. Instead passing object by move should be built into the language - each class should be moveable by default with proper support in the language

throwaway38294 commented on Cloudflare outage on November 18, 2025 post mortem blog.cloudflare.com/18-no... · Posted by u/eastdakota

ojosilva · 4 months ago

This is the multi-million dollar .unwrap() story. In a critical path of infrastructure serving a significant chunk of the internet, calling .unwrap() on a Result means you're saying "this can never fail, and if it does, crash the thread immediately."The Rust compiler forced them to acknowledge this could fail (that's what Result is for), but they explicitly chose to panic instead of handle it gracefully. This is textbook "parse, don't validate" anti-pattern.

I know, this is "Monday morning quarterbacking", but that's what you get for an outage this big that had me tied up for half a day.

throwaway38294 · 4 months ago

This is a bummer. The unwrap()'ing function already returned a result and should have just propagated the error. Presumably the caller could have handled more sensibly than just panic'ing.

throwaway38294 commented on Core Devices keeps stealing our work rebble.io/2025/11/17/core... · Posted by u/jdauriemma

throwaway38294 · 4 months ago

Bummer. I preordered a Time 2 but I'll just cancel if the company is going to screw over the community that kept them alive.

u/throwaway38294

KarmaCake day9November 18, 2025View Original