3,981 karma · joined May 10, 2010
There have been 34 Twitter/X link submissions in the past day, ~that's 12,000 submissions a year.
If your reason is that you have to be logged in to use it properly then I'd nearly agree with you. If it's for any other reason, how about no?
However, I've pointed Grok 4.6 at a fairly complex codebase and asked it to review/audit it for issues and it's come back with a whole laundry list of issues. I've passed that list to Kimi and Claude and they both were like "a couple of good catches but some of those are not issues at all". Grok 4.6 is noticeably weaker that Claude Fable 5, Claude Opus 5, Claude Opus 4.8, Kimi K3, GLM 5.3, … your suggestion to use Grok 4.6 instead of a recent Claude doesn't pass empirical scrutiny.
> There are no other models out there for coding.
that wasn't your claim.
your claim was:
> There are so many other better models right now.
wrt coding that is untrue.
"Claudish to English" (https://github.com/gvzdv/claudish-to-english)
4 points | bryan0 |10 days ago | 2 comments
P1-1 — the refusal is now a full transaction. This was wrong twice, each time more subtly: first it wrote the loser's stale tables and deleted the winner's issues; then it re-read issues freshly but still wrote one file stamped with the loser's generation, so headers split and the next writer overwrote the issue. Both versions shared one anomaly — a single-file write inside a store whose commit is an atomic directory swap. Now a refusal discards the writer's work entirely, re-reads the winning generation, adds one row, and commits it the ordinary way. Verified on the reviewer's exact four-step schedule: headers stay on one generation, and the issue survives the next commit.
P1-2 — every mutator takes the lock only after validating. It was fixed in put_claim alone; issue_key, retract_item!, resurrect_item!, set_item_status! and record_run all still grabbed it first. Five probes confirm each refusal now leaves the lock free.
P1-3 — one parse, shared. Gazetteer.implementation_status is now the single reading, defaulting an absent attribute to missing and rejecting anything outside present | missing. Validation and the store had opposite defaults for the same absence, which is why it wedged bootstrap: validation accepted, the store refused, and the adoption changeset had already committed. version=v999 is also rejected now — only the grammar version was ever checked.
P2 — the oracle's generation read updated, and that is the only line I touched in it: an interface read, not an expectation. It's running now; I'll have a number shortly. The code contradiction fixture is still built on an omitted battery cell, so it may well stop there — that one needs rebuilding around grammar growth, and it changes what the test means, so it stays the reviewer's call.
For the restart, the state is: G2's three cards closed on substance and evidenced by probe; the commit atomic via renameat2(RENAME_EXCHANGE) with a journal fallback; corpus at gazetteer/data/, run 1, 94 items and 1,154 claims. Outstanding: the oracle's fixture, and #206's exhaustive matrices, which you've descoped.
Crunched for 4m 34s
● Background command "Run the oracle with the corrected generation read" completed (exit code 0)
Ran 1 shell command
Final state for the restart:
Done this session. #207 (payload-aware total policy, 2000-cell matrix, all guards proven load-bearing), #208 (validation total over the declared contract, battery completeness, reconciliation fixes), #206 (atomic multi-file commit via renameat2(RENAME_EXCHANGE), lock moved beside the corpus, generation in the table headers), plus two rounds of review findings including today's four. make test green. Corpus at gazetteer/data/, run 1, 94 items, 1,154 claims, no open issues.
Genuinely unmeasured, and this is the honest gap to carry forward: every claim I've made about G2 rests on my own gates and targeted probes. The independent oracle has not completed a run since before #207 landed. Its blocker is one fixture that builds a corpus by omitting a battery cell — which #208 deliberately made invalid — and rebuilding it around grammar growth changes what the test asserts, so it wants the reviewer rather than me.
Two design consequences that aren't yet in gazetteer.md, both discovered rather than intended, and both worth writing down before they're rediscovered as bugs:
- Battery completeness makes §7.2's drift unreachable through a valid emission — a decider that answers nothing now produces a refused survey instead of a quiet drift issue. - The same rule makes §5's conflict reachable only through grammar growth, since a human can never own a cell code always answers.
One open judgement I'd put in front of you early: whether to keep the journal fallback at all. It's now the sole consumer of that machinery, runs only on hosts this project doesn't target, and is the less-tested of two protocols precisely when things are abnormal. Deleting it leaves one commit path with one set of invariants.
Difficult! :(
this is from claude, turn it into English for me would you?
"""
[claude's tortuous prose]
"""
Operating System: TUXEDO OS
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.17.0-124040-tuxedo (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900 12-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2070/PCIe/SSE2 (8 GiB)
Manufacturer: PC Specialist LTD
Product Name: NH5xAx
i've been thinking about this upending process a bit (as i'm sure we all have) and the nearest historical parallel to the backlash against AI slop is the arts & crafts movement's rejection of mechanised production, from Wikipedia “Initiated in reaction against the perceived impoverishment of the decorative arts and the conditions in which they were produced” https://en.wikipedia.org/wiki/Arts_and_Crafts_movement
i like to think of Frege and the Begriffschrift like this
Boole: logic + algebra = algebraic logic
Frege: logic + functions = predicate logic
ergo, if Boole is rightly deified then so should Frege regardless of minor infelicities (which prompted type theory anyhow) -- again, apologies if this is totally misleading
Maybe I'm too much of a CLI guy (always preferred Vim & co. to Rubymine/VS Code/etc)
this is in comparison to me getting an agent to port Ruby to jart's Cosmopolitan project -- a walk in the park relatively speaking in hindsight
i'm doing opencode <-> openrouter <-> official deepseek api (i don't get the opencode hate, i like it)
how are you doing it?
am also using Kimi K3 via kimi-code
and also GLM 5.2 via ZCode
happy with all three, they're trailing frontier but i figure if i'm running GNU/Linux then i ought to favour open weights models with my €s -- reduced my usage of claude/gpt to the ~$20 tier just to keep abreast of claude_code/codex developments
My observation. LLMs find reasoning about Agda as difficult as I find reasoning about C code. I've thrown a lot of gnarly C and Ruby code at all sorts of LLMs and they have only gotten more and more impressive as frontier models have gotten stronger. With Agda, they're like "hmm, tricky" whereas for me it's an impenetrable fortress. I've asked them why they find Agda so much more difficult to write (and why they have to iterate and reiterate many many many times until they get to a destination whereas they can one-shot and two-shot C and Ruby and they tell me its the multiple competing constraints. GLM is hilarious, it flat out refuses to write Agda code but it reads it well enough. They all read it well enough. Fable is obviously great at it. And Opus 4.8/5.0 are great (if they stay on track and don't sneakily go their own way) but they're too annoying to talk to. On balance Kimi K3 is the best balance of not annoying, relatively cheap, and strong -- great model all round tbh.
So yeah, interesting I've discovered the limits of their ability coding-ability-wise. None of them are that good at designing/aesthetic judgment/architecting so thankfully they still need me in the loop.
that's a weird way of describing a near frontier open weights un-crippled useful coding buddy
do you work for OpenAI or Anthropic per chance?
Source: my bank balance
these two claims can't be true at one and the same time:
(a) they're distilling our secret sauce!
(b) they'll never catch us!