Live data from Hacker News

Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

research.meta.ai

41–50 of 682 posts

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#43

Earlier quoted context omitted.

Pulled the trigger?

Common phrase.

That commenter you're replying to knows that. The original commenter before them wrote "pulled the plug" which is different and doesn't quite apply here (actually implies the opposite of what they meant to say).

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#44
post #5

Will be interesting to see how Qwen3.8 27B compares against this once it releases this week. Seems like dense 30B is back in fashion? EDIT: An open weight version of Muse Spark 1.2 is going to be released as well: https://x.com/alexandr_wang/status/2086756152034066792 https://xcancel.com/alexandr_wang/status/2086756152034066792

Yes, and also waiting for the next iteration of Gemma. Muse or Qwen are optimized for coding, while IMO Gemma is still better for non-coding tasks.

https://x.com/osanseviero/status/2086107547535122767

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#45
post #26

Earlier quoted context omitted.

I'm sooo happy I pulled the trigger on upgrading and getting a new laptop (with 64 GB RAM) last summer. Feels like it was just in time before the exponential price jumps.

Bought an M1 64 GB for 2000 euro’s second hand a year ago. That was sweet

paid 2.7k € for this same build new in Dec 2023, that was also sweet (still is)

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#46
post #5

Will be interesting to see how Qwen3.8 27B compares against this once it releases this week. Seems like dense 30B is back in fashion? EDIT: An open weight version of Muse Spark 1.2 is going to be released as well: https://x.com/alexandr_wang/status/2086756152034066792 https://xcancel.com/alexandr_wang/status/2086756152034066792

Based on the benchmarks, it seems that Muse Glimmer barely edges out against Qwen3.6 27B, except for tool-calling skills (MCP, etc.). I wouldn't be surprised if they released it now because they are afraid they wouldn't beat Qwen3.8 27B.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#47
It is interesting but it does look like a careful distillation of (Spark and) biggers open-weight models.

The progress compared to Qwen3.6 27B is good, not that impressive, it's a 4 months old model. (kuto to them to compare to 27B dense and not 35B MoE, it's more fair to do so). It is very probable that Qwen3.8 27B will crush Glimmer-30B on most benchmarks.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#48
post #4

Meta did not abandon opensource. I would love to see a smaller distill, or a moe of this size but the benchmarks seems competetive as long as it isnt benchmaxed witch i would not be suprosed if it is.

> Meta did not abandon opensource

Open weights*

I don't think outside of the Big 3 (Ant, OAI, GDM), given the strong competition from China, any other Lab has a chance at capturing the coding market if they aren't open weights (save for xAI whose latest Grok looks every bit good & will probably rely on Cursor for distribution instead of going open weights). There's literally no other selling point, as the capabilities have mostly converged by now among the chasing pack.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#49
As an industry, I wish we would stop calling these things "open weight" because it is too easy to confuse with actual "open source", which they are not.

Photoshop source code+ OSI license = open source

Photoshop binary you can run on your own computer = open weight

Photoshop SaaS web app = closed, proprietary (Opus, GPT, etc.)

"Open weight" models are still just binary blobs that are completely inscrutable. It's like bringing home a dog from the rescue and just hoping that it doesn't have a tendency to bite kids in the face. You just can't know. The only thing that you can do is try to add more training (fine tuning) telling it not to bite kids.

I don't think the FOSS community has ever accepted this, but somehow we're feeling like it is okay now.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#50
post #49

As an industry, I wish we would stop calling these things "open weight" because it is too easy to confuse with actual "open source", which they are not. Photoshop source code+ OSI license = open source Photoshop binary you can run on your own computer = open weight Photoshop SaaS web app = closed, proprietary (Opus, GPT, etc.) "Open weight" models are still just binary blobs that are completely inscrutable. It's like…

It is useful to indicate you can run the weights on your own hardware. That’s categorically different from most other commercial offerings. It’s as if your adobe example ignores the reality that would exist had photoshop been invented in 2019: cloud only.
Post reply on HN