there exist only 2^63-1 of them, no?

after yelling at a discord bot for hours, i realized this can be automated by making bots that yell at each other

i have an uncontrollable urge to burst into bitter laughter whenever i see "v1" in an api endpoint. stop being retarded and at least label it as v1.20251225 or something like that

it's such a pita in c, i can't sleep without -fno-strict-aliasing

spinning up a macos vm is pretty easy at this point, but only after years of effort in community projects like osx-kvm etc

maybe the reason that i'm both terminally addicted to llms while not anthropomorphizing them is that i never use voice mode of any sort. i don't even use any voice assistant to set alarms or do other shit. am i old or something

dario already hates kv cache to the extent of poisoning non-anthropic provider's cache, that's long before the 5min ttl adjustment

wasmtime's lastest changelog looks like this. i feel sorry for everyone still on copium to this day

don't forget to build with -boundschecks and -fllvm

thanks a lot for the kind offer. i know about the nixos review requests room and sent the link there and other maintainer have landed it. the process is still very not ideal (or the criteria of nixpkgs merge bot accepting a request)

another package that i maintain, i need to bump version and hash. can i land it with the bot? nope

someone else with committer rights needs to manually add it to merge queue, and bang it wipes out my commit author metadata! fantastic way of doing open source

the myth of nixpkgs contribution

me: i consent
maintainer: i consent
nixpkgs merge bot: i don't

isn't there somebody you forgot to ask

what the heck is *S-1-5-80-0,*S-1-5-99-0 and why am i reverse engineering some win32 .sys stuff in order to work on uh i don't know, haskell maybe?

instead of configuration.nix we have a 1k+ loc vibe coded powershell file with inline xml

i should make a meme that puts YOU CRASHED red letters on top of my windows vm install screen but i'm a bit exhausted

the litellm supply chain attack is a result of exposing ci secrets on the wrong granularity. any logic that uses secrets should live in an isolated downstream job, and github actions allowing people to be lazy and scope secrets to step instead of job levels is a footgun that will continue to fire

also, people talk about vibe coding already, but there's not nearly enough talks about vibe debugging and vibe profiling. runtime observability matters 100x more than type safety in many cases

my personal recent patch that i landed made i386 linux job shorten test time from over 1h to a few minutes by making python do less regex. did i brag about it already? but it's worth bragging about!

there are no low hanging fruits in making ci faster. a few minutes here, a few minutes there, keep staring at logs and wait for the eureka moment for another improvement

i've been rage sniped by the ghc project to do devops work

works in browser without extra bundling step, which matters when the js module lives in a non js project and you don't want to complicate the build/packaging logic with anything from npm

open weight models frozen in time is already "here to stay" by definition, and that's a very low baseline in different ways llms exist in the future

i couldn't run a concorde on my laptop

paradox of open source:

- do more work
- more work * same error rate = more errors
- more errors * other maintainers = more frustration

therefore, work harder = more frustration, q.e.d.

it doesn't count as vibe coding unless you can yell at your agent while crossing a road or picking up groceries

always have been

i think literal

it's burnout

why is lunduke so mad at rust. i mean rust is pretty diversified right, there's bro rust and there's woke rust