mleku on Nostr: the more work i do on nostr code, especially with unifying the front end and back end ...

the more work i do on nostr code, especially with unifying the front end and back end into the one language one codebase (i've switched to tinygo with some architectural widgets to structure the go code like moxie) the more that all the clanker is doing is recomposing *MY OWN CODE* that i wrote by hand. it found three tiny edge cases that in practice never happen in my json codec.

i suppose next thing that happens is i dig into the iskra database engine and translation algorithm, modify them manually and while doing it figure out how to do attention heads and interpolation and then after that it's clanker copypasta for me ser. and voila.

i mean, one day's work, in parallel with two other tasks, i've ported my orly relay's essential core features to build in tinygo, and the output is a binary of a bit over 4mb that does everything a vanila configuration of orly could do, except it was like, idk, 25mb or something.

when you know your code, and you code well, the clanker is just a fast refactoring tool that can do some smart things gluing stuff together.

the work i've done with building the design of moxie language has helped a lot too. the CSP/Actor architecture really does make everything like lego so once you have a widget that does one thing, you can just plop it in anywhere it would be appropriate, and bada bing bada boom.