TIL Stockfish in 16.1 dropped all classical evaluation heuristics in favour of NNUE (aka, a machine learned evaluation function).
I get that it performs better, probably faster, definitely less code, but some serious explainability was lost.
Proposal: let’s measure model evaluation/generation speed in baud instead of tokens/sec. Remove the encoding from the unit calculation.
Watching deepseek-r1:671b run locally on my AI box (the 1.58 quant version, I’m not a billionaire) is like catting a file over 900 baud.
At 4 tokens per 3 words on average — and I’m getting about 4 tok/s — it’s really, back of napkin, ~50 baud
It’ll be good to have you in town. 😁
Shame it’s not the East Bay, but then, I never lived in Brooklyn either 😜
The biggest winner of the AI race will be distributed systems people. Everything is converging onto a distributed network of stuff and it is only accelerating in the last two years.
I get it that merges can be done better than git by preserving commit identity— as I understand it, hg did, and jj does it with its tracking ids.
Pithily, merge commits are a penance for thinking in the SVN sense of version control (I’m old) — but hopefully now we, ahem, `evolve` (pun intended)
In another weird way, this is why I came around to rebasing/squash-merging over merge commits in git.
It was `git rerere` that changed that for me, and why that’s not default in git baffles me.
An interesting emergent property of switching to jujutsu for version control is I have more active ‘branches’ and even empty-but-described commits with “what I intend to do here”
Because the rebases are so powerful and cheap, I can get code & thoughts out of my head and worry about merging later.
The abandoned sentence was the affect that “at least they can work together”
I could give a damn about the feature speed of alacritty (pun not intended) — at least the devs
He’s really not nice, you’ve had similar experiences, and so, you make your own decisions, but he’s on my ban list, and will avoid his code whenever possible.
Alacritty stan here, which I arrived on for multiple reasons, but one is because the kitty dev is on my very short blacklist.
(As ghostty gets better, I'm open to the alternative)
Fuck. Forgot an equals sign. Y’all, programming, you’ll always have bugs no matter how far you get.
Sometimes the snark takes over in the comments, but you’re still gonna be helpful.
Anything in the modern era must interface with git… and it does. You do have to remember you’re viewing a superset compared to your git-using peers but my goodness is it convenient
I am become a jujutsu convert. Rebasing whole branches on a whim is what I’ve always wanted. jj-vcs.github.io/jj/latest
My snarky point is mostly that people won’t hate you for it, compile times come with the territory 🙂
When writing Rust, you’re already conceding the compile time question. 😜
Ergonomics for sure. I’ve seen “quick start” snippets containing `unsafe` blocks 😞
Imagine trying to tell @filippo.abyssdomain.expert about Linux 😳
(Also, yep, Home version, I knew that trivia)
Watching dog shows at the bar and the Pekingese shows up…
“Ma’am, that’s a tribble” 😂
(All dogs are good dogs, some are tribbles, and honestly, not my taste either)
“Avocado Toast” should be called a “Croque de Californie”. In this essay, I will…
Yeah, I've been doing the ollama thing, and built a GPU rig for it. It's fun!
Step into the web of open models and running your own… 😈
Which one?!
Back in my day, we called it ‘trunk’ :old-man-shakes-fist-at-cloud:
TFW you use a right-wing jerkwad’s useful blog post for the opposite (in this case rename git master->main instead of the reverse (because ‘main’ is apparently offensive to dumbasses))
I used the phrase “is that the 411?” semi-sarcastically today and got blank stares.
I’m sorry. I grew up in the late 90s. Phones used to be phones.
We mustn’t dwell. No, not today. We can’t!
I've found myself adding "(Barak's Version)" to all my forks, READMEs or design docs that explicitly don't take contributions or are too salty to share (h/t Taylor Swift) 🙃
I kinda wish we had “license shorthands, but for contribution rules” — generally, BSD/MIT are viewed as permissive, Apache2 with corporate, AGPL is what it is, CC-BY-NC-SA, etc
Ranging from “no contributions, gfy”, “no PRs without an issue first”, “PRs welcome”, to “fuck it merge it, anarchy”
Maybe I’m getting jaded but so much of project planning comes down to “is it big? Or is it _not_ big?”