convoluted connor @notwa@witches.town

something interesting is that, if you are gonna use x/17 for coordinates, 255/17 is exactly 15 and 65535/17 is exactly 3855. seems like this works for any 2**(8*Z)-1

i think i broke wolfram https://witches.town/media/x_XPZkqAQDfgtqJfVd0

i was thinking about using integers for some grid-based distance stuff just for sanity — and perhaps portability to retro consoles…
the 24/17 one is nice, because you can do 12/17 and approx invsqrt(2). only problem is dividing by 17 when the time comes.

random observation: 17/12 is just slightly over sqrt(2), and 24/17 is just as close but slightly under instead. there's an absolute error of 0.00245 in both cases, and both are ~6 times more accurate than a simple 14/10.

pretty kitty

something I've been considering is making a reference of math functions and their basic properties for creative applications. often times I can visualize the f(x) curve I need in my head, but then I have to remember what functions even produce curves like that. they'd be roughly normalized too so you can pipe them more easily

bee splines

whenever i'm just staring at something online, my brain starts yelling at me like "come on connor, fuckin' do something already! do the thing!" and then i open a hundred things (tabs, files, projects) and try to settle on one of them

"we'd like to hear how you're using our APIs" gosh darnit Dropbox I only have a dev account so I can manage files from my raspi, because last time I checked, you don't provide a first party ARM client

Kirkland signature guitar pickups

The wind has gotten damp-goro...
Tomorrow is rain-goro...
Goro-goro...

I didn't really mean nor want this to be an account full of mathy or techy things but here we are

b-splines seem to be described a lot more complicated than they really are... even on this page that manages to describe bezier curves relatively casually

a determinant of determinants...

msys2 somehow broke printf in awk :shrug: