I can't imagine concentrating on a complicated project like that on the go, but I went back to stare in awe at said picture and I think its a train or bus. Still a flex.
I think the author addresses this in saying that since AI output is statistically plausible by design its unlikely to improve in this area. Why do you think AI will get better in this way?
Its a shame there isn't more goodwill for some companies to bankroll a project like asahi linux. Keeping up with reverse engineering apple silicon seems like a very large task.
Risk limiting audits are why this work. You physically sample ballots at random. The number you sample grows as the gap in the electronic tally shrinks to reach high confidence the election was tabulated correctly.
Honestly seems like zig is shaping up to be a better fit for kernel. Regardless the language that attracts skilled kernel devs will matter more then lang.
Gokrazy is a minimal linux distro that just boots into a go init program. You can run on a raspberry pi or pc. It has a little init system that just takes a path you normally use in `go run` and just runs them and restarts as needed. Its been a joy for me to play around with. Has A/B updates as well.
I feel like wc3 is undersung. To me it achieved the perfect balance of allowing potentially mechanically worse players to win with brilliant tactics or strategy. It put the emphasis on strategy in rts more then anything else.
As a kid I was shit at it and played customs maps and goofed with the editor. Now I've gone back to find grubby streaming and revealing the depths of the meta evolution, and counters.
I like that even when a strong meta develops people can potentially counter with strategies that aren't as well rounded for long term use but upset the current meta.
I think its fundamentally more difficult to host communications services where spam is possible and there is no auth/contact system in place before first communication can happen.
I see the desire to avoid mucking with control flow so much but something about check/handle just seemed so elegant to me in semi-complex error flows. I might be the only one who would have preferred that over accepting generics.
I can't remember at this point because there were so many similar proposals but I think there was a further iteration of check/handle that I liked better possibly but i'm obviously not invested anymore.