one of the things that all the me-toos of systems dev and their fawning adoration for rust, and i'm being realistic about Go these days since i've succeeded in making an early-beta grade cut down version that addresses all of the issues i found with go. but...

rust's mascot is a crab

crabs most notable behaviours are dodging sideways and grabbing onto adversaries and pinning themselves to them with heavily armored pincers.

the latin word for crab is cancer

the disease, cancer, tame from the way that its structure resembles the shape of a crab, and the way that it so persistently anchors itself to the body. it's not an invader, it's a big blob of corruption that is extremely hard to dislodge.

i think that says a lot.

i have some hard criticisms about Go now, and Go inherited these because Google wanted Go to be a replacement for C++ and thus has the same shitty multithreading and parallelism problems, that the go devs tried to simplify and in the process made them more liable to develop subtle concurrency problems due to the composite of CSP concurrency and shared memory parallelism.

i hate all of them but cancer the crab and the cancer of rust's ugly, seething mass of annotations and complex memory management notation create are at least as bad as the concurrency errors that commonly show up in Go code except with Go you can pare down the concurrency to avoid most of that, like i did with Orly. whereas, with Rust, you have a different problem - there's no strong model of event driven processing and message passing concurrency, it uses the same shared memory problem which means when you do concurrency in rust, you get the same issues, it's just literally harder to do concurrency in rust.

C, C++, Rust, Go, Kotlin, Java, Python, javascript. each one of them is cancer, in one way or another. but Rust literally adopted the literal animal tied to the original source of the word cancer, and its messy structure, the cultish mindset of its users and advocates are abominations in the field of computer science.

of course the real source of the problem is in the government-corporate mindset. rust just has the worst of all of them.

anyway, on that note, i'm actually recommending to port a nodejs server into rust, to simplify the codebase. hah.

i hope i don't catch cancer out of it tho.

@nextwave fyi, i have quit using signal after discovering things about its on-disk encryption. use matrix to contact me: @smeshlol:matrix.org

the longer i use nostr and its cryptographic identities the more alarming and threatening kyc processes become.

they were always threatening, but when you know they are unnecessary, they also become alarming.

the clear need to get businesses using nostr-like identity systems (and why not just use nostr auth anyway, really) gets more clear every time i am photographing my id documents and doing selfies. all of this - and google's 20 different identification systems, just show that they understand there is need for a strong system of identification, but the existence of solutions decades old that are just not even on the agenda.

feels like they are just pushing the issue so eventually you just go "ooook then just fucking inject me with a permanent fucking cattle tag already"

that's a nope from me.

i've done it today twice for things that are also both already solved problems in my experience but the crabwalking mainstream of software as a service isn't doing this to actually manage a sybil defense mechanism. it's a compliance mechanism.