News for hackers. Stuff that matters.
Re:GPT‑5.3‑Codex‑Spark by dotancohen on Friday February 13, 2026 @12:51AM (#46999359)

  > 46,255 mm²
To be clear: that's the thousandths separator, not the Nordic decimal. It's the size of a cat, not the size of a thumbnail.
Re:GPT‑5.3‑Codex‑Spark by ash_091 on Friday February 13, 2026 @03:57AM (#47000559)
*thousands, not thousandths, right?

The correct number is fourty six thousand, two hundred and fifty five square mm.

Re:GPT‑5.3‑Codex‑Spark by c0balt on Friday February 13, 2026 @07:15AM (#47001849)
or about 0.23 furlongs
Re:GPT‑5.3‑Codex‑Spark by fifilura on Friday February 13, 2026 @07:39AM (#47002029)
More like one thousanth percent of an acre.

(wow, that is not much?)

Re:GPT‑5.3‑Codex‑Spark by tshaddox on Friday February 13, 2026 @09:24AM (#47003090)
Whoa, I just realized that the comma is the thousands separator when writing out the number in English words.
Re:GPT‑5.3‑Codex‑Spark by shwetanshu21 on Friday February 13, 2026 @12:57AM (#46999391)
Thanks, I was acutally wondering how would someone even manage to make that big a chip.
Re:GPT‑5.3‑Codex‑Spark by jmalicki on Friday February 13, 2026 @09:56AM (#47003418)
It's a whole wafer. Basically all chips are made on wafers that big, but normally it's a lot of different chips, you cut the wafer into small chips and throw the bad ones away.

Cerebras has other ways of marking the defects so they don't affect things.

Re:GPT‑5.3‑Codex‑Spark by Sharparam on Friday February 13, 2026 @07:44AM (#47002085)
This is why space is the only acceptable thousands/grouping separator (a non-breaking space when possible). Avoids any confusion.
Re:GPT‑5.3‑Codex‑Spark by fcanesin on Friday February 13, 2026 @07:57AM (#47002212)
46_255
Re:GPT‑5.3‑Codex‑Spark by xyproto on Friday February 13, 2026 @08:30AM (#47002478)
Space is also confusing! Then it looks like two separate numbers.

Underscore (_) is already used as a decimal separator in programming languages and Mathematics should just adopt it, IMO.

Re:GPT‑5.3‑Codex‑Spark by awakeasleep on Friday February 13, 2026 @08:49AM (#47002676)
A competing format to simplify things?
Re:GPT‑5.3‑Codex‑Spark by bhaak on Friday February 13, 2026 @10:36AM (#47003887)
A competing format that is understandable to probably everybody.

An ISO 8601 date is also comprehensible to anybody even if they never seen it before and have to figure it out themselves.

Re:GPT‑5.3‑Codex‑Spark by fifilura on Friday February 13, 2026 @11:11AM (#47004318)
Re:GPT‑5.3‑Codex‑Spark by bhaak on Friday February 13, 2026 @04:48PM (#47008283)
I said date. Not time, not timestamp, not period, not week, not range, not ordinal date.

Just date.

Re:GPT‑5.3‑Codex‑Spark by ultratalk on Friday February 13, 2026 @10:03AM (#47003506)
Re:GPT‑5.3‑Codex‑Spark by wvbdmp on Friday February 13, 2026 @09:02AM (#47002804)
You mean thousands separator, yes? Agreed, it’s annoying when languages don’t have this feature.
Re:GPT‑5.3‑Codex‑Spark by xyproto on Monday February 16, 2026 @11:45AM (#47037191)
Ah yes, thousands separator.
Re:GPT‑5.3‑Codex‑Spark by wongarsu on Friday February 13, 2026 @10:44AM (#47003998)
A thin non-breaking space also clears up the confusion without the visual clutter of the underscore. It's just inconvenient to use
Re:GPT‑5.3‑Codex‑Spark by mulmen on Friday February 13, 2026 @02:23PM (#47006632)
The problem is our primitive text representation online. The formatting should be localized but there’s not a number type I can easily insert inline in a text box.