Robey ☠️ @robey@mastodon.technology

(to the tune of "rubber ducky")

honey mustard, you're the one
you make nuggies so much fun
honey mustard
i'm awfully fond of youuuu

oooooooof! how many times do we have to point out that "count" is the prototypical example of an english word that you do NOT want to abrvt

i do think there's also a "celery-taster" aspect too

some of us cant abide by the visual noise of using parens for ALL syntax... others dont really taste that and dont mind it

this gives an interesting upsight into why some people get so excited by lisps... it may be their first experience using a high-level language to solve real problems

for others of us, that was python or typescript

if i were the market, i would simply solve all problems, perfectly, with an invisible hand

i just learned that google started deleting the dejanews usenet archives and it makes me inconsolably sad

why not hand it over to archive.org if it's too much trouble anymore?

in my dream there was a lip gloss called "the fading light of a dying star"

what i'm saying is that if you spent your childhood with only 3 registers, you treasure them like they were your own children

current status: yelling at a ben eater video that he can just do `LDX message,Y` he doesnt have to keep doing `LDA message,Y` and `TAX`

have you ever 65c02 bro?!?!?!

also mildly offended at using the painters algorithm to reverse a string

stack overflow:

Q. should you compress before encrypting?

A. yes. *edit 4 years later*: no.

ahhhh stack overflow! never change! *edit*: always change!

here's your requisite meme

but if that optimization matters a lot, js can do it too. *and* it won't have to copy a buffer into the wasm sandbox. turns out that makes it even faster, because the copying was now (always?) the bottleneck.

9_521_943'th piece of evidence that the slow code is _never_ what you thought it was.

still very excited by assemblyscript. porting was very simple and i can see this being useful for cpu-intensive tasks. thanks @brion for calling attention to it!

3/3

the original version byte-scanned buffers and did a lot of `slice` and `concat` to keep the logic simple. the hash itself does a lot of bit operations like "rotate", which are awkward in js.

for wasm, passing memory across the js/wasm border is the awkward part, so i tuned the algorithm to track more internal state, receive a buffer, and return "you should cut it here". no `slice` or `concat`.

2/3