Notices by dram🎀 (dramforever@mastodon.social)

@whitequark pmods can run differential pairs. i've always wanted to try to get pmod hdmi working. granted, hdmi can tolerate a bit more BER

there's no standard on how the pins pair up on a pmod so that's always fun.

@whitequark yessssssssss!

@whitequark i've been thinking about this since i first saw your post. on one hand i'm incredibly thankful for having teachers in various senses of the word drill into me that it's never "rule of law", and the law serves the rule. on the other hand, i really don't know what i can do about it.

@whitequark there was this one thing i heard where someone wrote a bitstream to an fpga to have every pin blast out its own name in UART but i can't find it

@whitequark ah, so *this* is what an MCE is...

@whitequark why

@whitequark @0xabad1dea for me it was third year, which is basically when they ramp up to full on compsci in the undergrad program

@whitequark @ajn142 chinese "(" girl meets russian ")" girl

Your daily reminder that Ferris the crab is NOT telling you when writing Rust, you have to structure your data in a neat tree and you deserve to go to hell for daring to reference nodes crossing branches.

It's telling you these references should not be pointers with random lifetimes.

There's nothing wrong with graphs with nodes labelled with `&'arena RefCell<Node>` or really, just `usize`.

@whitequark i can't tell if this is better or worse than the time someone unironically told me "all of these are monads, you just need to rewrite them in continuation-passing style"

we have four value logic at home

@whitequark maybe use tracing events to see how many SIGINTs are sent?

echo 1 | sudo tee /sys/kernel/tracing/events/signal/signal_generate/enable
sudo cat /sys/kernel/debug/tracing/trace_pipe

@whitequark now i wonder if you can subclass list to make it not quadratic

@whitequark i had an idea... and yup

while True:
match args:
case [ '--foo', foo, *args ]:
print('foo', foo)
case [ '--baz', *args ]:
print('baz')
case [ '--', *args ]:
break
case [ arg, *args ] if arg.startswith('-'):
print('Unrecognized', arg)
raise RuntimeError() # FIXME

# This can't be case _:
# Otherwise previous case overwrites args
case args:
break

@whitequark maybe a bad data point but i can only think od https://www.sifive.com/boards/hifive-unleashed

we spent so long joking that the three sifive devboards are "unleashed, unmatched, unfinished"

TIL about "we have CAR-T at home" /pos
https://www.cell.com/trends/biotechnology/fulltext/S0167-7799(23)00239-1

> Arming immune cells via CAR-encoding mRNA represents an emerging direction in immunotherapy, enabling in vivo generation of CAR cells with minimum risk of transgene integration.

@whitequark that makes sense, and also matches my haven't-ever-used-lvm intuition that it seems a bit sketchy...

@whitequark i found some anecdote that "thin-provisioned LVM snapshots" work well. i don't know if you can smoothly start using this

@whitequark even for things with no back up, i personally run 15-minutely btrbk btrfs snapshots with decaying retention for earlier files. snapshots like these take minimal time to create and help with being able to create backup in a more consistent state

i will probably switch to zfs for my next computer/drive, whichever comes first, but the principle is the same.

ofc this depends on fs support. i'm not aware if lvm is capable of doing this on a block dev but it sounds sketchy

The existence of Nintendo 64 implies the existence of Nintendo N32 and Nintendo O32