(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

abusive sexual word used in code 

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

academic paper style, implied joke violence 

me, to the inventor of two-column LaTeX-generated PDFs: "You don't know who I am, but know that I have a certain set of skills. I will use these skills to find you, and make you suffer until my text layout is freed. If you do not undo the last several decades of academic papers and release them all as single-column HTML, I will break you into tiny pieces and then stomp on the pieces."

Intel, ARM, IBM, AMD Processors Vulnerable to New Side-Channel Attacks arxiv.org/abs/2008.02307

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

Show thread

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

@robey archive.org already has a comprehensive usenet archive until 2013 (though not the dejanews dump), see https://archive.org/details/usenet-comp.lang and friends.

Also, if you mean the recent issue of comp.lang.forth and comp.lang.lisp being blocked, that wasn't deletion but disabled access due to spam (still a misconfiguration because the spam seems to come mostly through the google groups web interface) and has since been reinstated.

I can still find dejanews-era messages on groups.google.com, e.g. https://groups.google.com/g/comp.lang.forth/c/qbbATF1Y6HY/m/Okdt9HsSdR0J

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

Show thread

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

I think Google should save everyone a lot of time and effort and jump straight to discontinuing new services:

"We are proud to announce that Google Kitchen Tools will no longer be available on Sep 1st 2020, nor has it ever been available. Should you wish to export your Google Kitchen Tools data, you should be aware that there is no data, as Google Kitchen Tools has never existed.

The Google Kitchen Tools Team"

stack overflow:

Q. should you compress before encrypting?

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

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

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!


Show thread

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`.


Show thread
Show more
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!