‹ BackHN Continuity

Thread

Grok 4.7

609 points · 541 comments · meetpateltech

  1. moojacob · · focus · HN ↗
    Apparently Grok 4.7 has 40% more weights than Grok 4.6, but the price ($6 output token, $2 input) is the same.

    Given that the decrease in their margin and the fact they delayed the release of Grok 4.7 almost two weeks past the original date, XAI must not have been happy with the results for 4.7. And XAI also waited the day before Opus 5.5 is rumored to launch. I imagine Opus 5.5 will blow Grok 4.7 out of the water benchmark wise.

    However, I have become skeptical of benchmarks. Grok 4.5 solved some issues setting up a buildroot system that Fable 5 couldn't do. I find the post cursor groks are phenomenal at frontend web development, though Claude is much better at backend ruby.

    My favorite part of the new Groks has been how they speak in plain english. I simply cannot stand Claudish. Or even GPT, which doesn't have Claude's ticks but definitely likes to handwave explaining technical concepts. Still, nothing beats Claude 3.5 and 4 with explaining since it seems all models have regressed. I wonder if Grok 4.7 will also regress with English because of all the RL.

    1. atniomn · · focus · HN ↗
      I expect the next Anthropic release to finally reduce the prevalence of Claudish
      1. moojacob · · focus · HN ↗
        If they fix Claudish, they've earned me back as a max customer!

        Fable 5.1 is not there quite there yet.

        They need to get that Sonnet 3.5 magic back.

        1. rfgplk · · focus · HN ↗
          Same. The issue with Anthropics models is that (speaking regarding code generation) they REFUSE any kind of comment override instructions. I've tried everything and no matter what, after a few turns, they resort to generating the same overtly verbose junk. Bun's codebase is littered with them See

             // `HANDLE` is an opaque kernel handle (kernel32 validates and returns 0/FALSE
             // on a non-console handle); every out-param is `&mut T` to a `#[repr(C)]` POD,
             // ABI-identical to the Win32 `LP*` pointer (thin non-null). The reference type
             // encodes the only pointer-validity precondition, so `safe fn` discharges the
             // link-time proof. (`bun_windows_sys::kernel32` declares these with `*mut`;
             // redeclared locally so the legacy-conhost cursor path below is plain calls.)
          
          or

             // Progress's terminal handle is the canonical `output::File` (vtable-backed
             // stderr/File from `OutputSinkVTable`). The duplicate `ProgressTerminalVTable`
             // from B-0 round 1 is removed; tty/ansi/winsize route through    the new
             // `OutputSinkVTable` slots so `bun_core` stays T0 (no `bun_sys` dep).
          
          from src/bun_core/Progress.rs
          1. mrieck · · focus · HN ↗
            The longer the comments, the more watermarked the codebase becomes.
          2. r_lee · · focus · HN ↗
            > The reference type encodes the only pointer-validity precondition, so `safe fn` discharges the link-time proof.

            just reading this gives me a headache

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.