implr
Cursed Computer Connoisseur
@ https://x.com/dragonsectorctf, BGP shitposter @bgpwtf@social.hackerspace.pl
a true gem
(Gaming Electron Microscope)
@whitequark@mastodon.social @HalvarFlake@mastodon.social while doomscrolling the musk website earlier i saw a vibecoder bro's take that went something like:
in the future there'll be no libraries, don't need them when claude will just generate a quicksort or whatever within your project
and i think this is quite revealing. llms will let you vibe a medium-sized (within context size) project, but none of that code will be reusable, or reuse other code. you won't extract and publish bits of it standalone because it's all slop.
RE: @implr@social.hackerspace.pl
i should finally get around to reporting the zfs catastrophe this causes as a bug
device falls of the bus, kernel removes it, any zfs kthread that tried to touch that pool gets stuck, any userspace io ends in D, can't even export the pool
- i got frustrated in my first manual attempt, so probably not. if i got to the reading kernel source part (what the llm did) it'd be interesting but still frustrating because:
- there wasn't even a code mistake, it's purely user error. i flipped the wrong kconfig flag months ago and didn't know. so i'd be pretty angry at myself
@kbm0@mastodon.social @whitequark@social.treehouse.systems @azonenberg@ioc.exchange is it really still cheap? I've been a refurb enterprise flash enjoyer but all the usual places got the same price rise as the new market
@jripley@mastodon.social
Yes, a BF2/3 is basically a rpi4 or 5 glued to a cx4 NIC, with power use higher than both of those.
However, I don't think it's fair to compare an old bluefield with a modern x86 host. The newer incarnations have Neoverse V2 cores which should be just as (if not more) efficient than current x86.
There's a reason most hyperscalers use a variant of this tech for their clouds, and they're extremely sensitive to power OPEX.