11 comments

  • montroser 50 minutes ago
    Hoping this is real. It's too bad to see the signals from Qwen that they will not be releasing a 35B-A3B for the 3.8 lineup. The MoE architecture makes a huge difference for being able to run these local models on reasonable consumer hardware.
    • parsimo2010 29 minutes ago
      Honest question/suggestion for the HN audience- Since Qwen released the weights for Qwen3.8 2.4T-A95B and we already have the staring point of Qwen3.6 35B-A3B, couldn't someone distill the bigger model and make a "pseudo" Qwen3.8 35B-A3B? Sure, it wouldn't be an official Qwen release but couldn't someone improve on Qwen 3.6 and get the thing everyone is asking for?

      I am calling this a suggestion for the audience because I don't have the will/resources to do this.

  • garo-pro 10 minutes ago
    Across five cases it reliably claims to be Claude without being able to name a specific version.
  • jonesy827 1 hour ago
    I've been using the 35B-A3B today for some web scraping work, and it has been on par with Qwen3.8 27B at a much higher speed and at a higher quant (q4 vs q8). I'm impressed.
    • jakswa 38 minutes ago
      I had to go down to UD-Q3_K_XL for Qwen 3.8 27B to get it to fit in VRAM and be usable, but I worry I'm gutting its intelligence somewhat. I too am interested in faster + more-usable alternative that can exchange blows with the Q3-dumbed 27B.
    • jadbox 1 hour ago
      I need someone to run actual benchmarks between the two.
      • NitpickLawyer 2 minutes ago
        Only relevant benchmarks are those you make yourself, targeted specifically for your workflows. Anything else is just number go up on a pretty graph, and every model out there is probably benchmaxxed to hell on the public ones anyway. Keep yours private.
      • swatcoder 53 minutes ago
        Benchmarks are the BMI of model evaluation.

        They may have utility in trying to look at the whole landscape of models, but are very misleading when it comes to making 1:1 comparisons or in developing confidence at to how a given model will deliver on your workflow.

  • prometheus1992 1 hour ago
    Can't wait to try this. Ornith1 (9B) was a really nice model. I have been running it locally using - https://github.com/deepanwadhwa/samosa-chat
  • colingauvin 30 minutes ago
    397 is just too big for two Sparks even at NVFP4. Wish they had made this just a tiny bit smaller.
    • kees99 0 minutes ago
      Ornith-1.5 is derived from Qwen3.5 via post-training. That process has to preserve exact parameter count.
  • bigcat12345678 1 hour ago
    How is ornith-1.5's base model developed? Is the base model one of the Open weights models, or one pre trained by ornith team from scratch? I couldn't find information to answer this question in the article.
    • goldemerald 1 hour ago
      It looks like they post-trained Qwen3.6. Interesting to see how far they could improve it with they harness/algorithm.
  • nextaccountic 1 hour ago
    Is this open weights? Or planned to be
  • wyre 25 minutes ago
    This is exciting.

    Their 9B model benchmarks competitively with Sonnet 4 which is pretty cool to have such a small model compared to one that came out 10 months ago.

    I’m curious how providers will price their 397B model.

  • jakswa 49 minutes ago
    I'll be comparing the 9B vs Ling 3 Tiny (8B-A1B) as a scout model. Ling tiny is so fast but can be a little too dumb. Hope the 9B strikes a good middleground even if dense/slower.
  • tangjurine 1 hour ago
    This looks cool