Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Alphabet as a Sequence Engine: A Census of What Letter Names Generate, and What the OEIS Has Never Seen

Abstract We evaluate the integer sequences generated across 36 human writing systems under the Engineering of Alphabets (EOA) operator. Auditing all 1,056 resulting sequences against the On-Line Encyclopedia of Integer Sequences (OEIS), three facts survive every check we could devise. First, the growth rates of these sequences cluster on a small set of exact algebraic numbers 2.618…, 3.414…,…

This census investigates the integer sequences produced by 36 human writing systems using a fixed recursive expansion rule applied to each letter's name. Across 1,056 resulting sequences, three key facts emerge:

First, the growth rates of these sequences align closely with a small set of algebraic numbers: 2.618..., 3.414..., 2.414..., 2, and 3, with 2.618... (the square of the golden ratio, φ²) appearing most frequently.

Second, several of the generated sequences correspond directly to well-known mathematical series, including the powers of two, Fibonacci bisections, Lucas bisections, Pell numbers, Mersenne numbers, and the series of counting numbers.

Third, 388 distinct sequences generated by the scripts do not appear in the On-Line Encyclopedia of Integer Sequences (OEIS), suggesting these patterns may be unique. Two random baseline controls tested to confirm the rarity of these findings were: random alphabets of matched size never produce the core patterns found in natural scripts (0 of 250 simulations), and the English E5 alphabet splits into two equal halves, a pattern not seen in random alphabets (0 of 100 simulations).

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

62% vs 58% on the Same Benchmark: How Many Tasks Before the Gap Means Anything?

Two teams run the same agent benchmark on the same model with the same scaffold. Team A runs 100 tasks and reports 62%. Team B runs 250 and reports 58%. Both publish their task lists and pass rates.

  • The 62% vs 58% benchmark gap may be misleading.
  • Researchers analyzed four benchmarks: AppWorld, tau-bench, SWE-bench Verified, and SWE-bench Lite.

Scaling Real-Time Stream Chat in Go: In-Memory Hubs, WebSockets, and Redis Pub/Sub

Live stream chat is deceptively hard. What starts as "just broadcast messages to connected clients" becomes a distributed systems problem the moment you scale past a single server instance.

  • In-memory WebSocket hub per process for local speed and efficiency
  • Redis Pub/Sub for cross-instance fan-out and horizontal scalability
  • Each instance maintains client map with single goroutine to avoid data races

More from Tuesday 27 October →