Viewing profile — blegr

I’ve seen him discuss additions to the static typing features.

Same as a bank? If you lie to investors and get yourself nuked, the owners or what passes for owners get wiped out, which is normal. The people who really qualify as victims are th…

> The police spent the day searching her house. Inside, they found a note with the heading “NOT GOOD ENOUGH.” There were several phrases scrawled across the page at random angles a…

New link: https://www.newyorker.com/magazine/2024/05/20/lucy-letby-was...

Some people feel some kind of person/presence close to them, that's how it happened to me. This [1] weirdly makes sense. It felt kind of like those dreams where you can't move. Exc…

A lot of suspicious facts in the article though. > Letby’s defense team said that it had found at least two other incidents that seemed to meet the same criteria of suspiciousness …

Does this make MRIs safe for some people who wouldn’t qualify due to metal implants? Or at least reduce the risk of accidents?

It's funny that restaurant burger prices in my EU country are basically the same as in your "upscale American city". I thought everything there was more expensive since the higher …

Didn't Microsoft stop using those in BitLocker years ago because they were often borked? [1] It's a new failure point, but it's sensible. [1] https://www.tomshardware.com/news/bitl…

Good design dictates that you start one loop and build the whole program around it, no? The docs for asyncio.run say as much.

It’s not about the price of upgrades though, it’s about their bundling together and the ridiculously stingy base specs that often make the upgrade non-optional. People who buy a ba…

I hope this means AI-accelerated frameworks get better support on Mx. Unified memory and Metal are a pretty good alternative for local deep learning development.

Yes, but you understood what I meant since you could assert that it’s not what it means.

It forces you to buy multiple upgrades instead of just the one you need.

Now that GP said it, it'd be nice to be able to write "some_map[i].value_or(some_value)".

I see your point, but my experience is that you need the stack trace first, and the developer’s explanation second. Asserts crashing with a message that makes perfect sense in its …

Right, but that's redundant with the stack trace. It's not actually helpful to run a big program I don't know very well and panic with a single "your goose isn't cromulent!" messag…

It's not really my choice, I'm working in a big codebase I didn't write. Lots of large classes containing large collections with getters and setters.

It sucks but it's easy to review and avoid, probably could be checked statically by linters too.

> The Option type seems to have various standard Rust methods like expect() Isn't that value()?