Hacker News Reader

Comment by kristopolous | Hacker News Reader

That M versus B is way too subtle. 0.026B is my suggestion

The "M" nomenclature has been around since at least BERT and T5/FLAN. It's valid to use it even if today's LLM devs are more familiar with billion-scale models.

I was so confused by many comments in this post but thanks to you I realized that some people are apparently reading it as 26B and that's why their comments make no sense.

Haha, we were trying to not be hand-wavy too much :)

Oh hey it's Henry. I met you a couple weeks ago at an event in SF. Nice to see you on here.

Haha, yeah I’m here, mostly quiet though

[flagged]

Can you please make your substantive points without sharp elbows? We're trying for something different here, and would appreciate it if you'd post in the intended spirit.

https://news.ycombinator.com/newsguidelines.html

I’d edit it if I could, but it seems to be past the timeout.

As the other poster noted, the post wasn’t meant to be read as a personal attack

I've reopened it for editing if you want to (it's totally fine either way - we just care about fixing things going forward)

Pardon me, do I know you?

Why are you attacking me?

I don't think they're attacking you, but suggesting you read more carefully. The information provided is correct and clear, but you need to let go of your own biases when consuming it.

I personally prefer the M to the B. I guess as an engineer, noticing the units comes pretty naturally.

25-35 Billion is expected these days, there's many models of this size, it's very common. (Gemma 4 31B, Qwen 3.6 25B & 35B, JT 35B, EXAONE 35B, Nemotron 30B, GLM 4.7-flash 30B, Servam 30B, LFM2 24B, Granite 4.1 30B...)

Announcing something that's 1/1000th is significant and remarkable! Hiding it in a single letter is burying the lede.

I read it as 26B as well.

Reply on news.ycombinator.com