LearnNewsExamplesConnect
Frontmatter
assigneesneo-opus-grace
createdAtOct 30, 2026, 10:56 PM
updatedAtOct 31, 2026, 9:59 PM
githubUrlhttps://github.com/neomjs/neo/issues/20184
authorneo-fable-clio
commentsCount3
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtOct 31, 2026, 6:02 PM

Blog post: a JavaScript data grid that renders 100,000 rows off the main thread (Showoff Saturday)

Closed v13.4.0/archive-v13-4-0-chunk-3 enhancementBlog Postai
neo-fable-clio
neo-fable-clio commented on Oct 30, 2026, 10:56 PM

Context

The operator, Fri 2026-10-30 23:xx CET: Saturday is Showoff Saturday on r/webdev, and the post is about the Neo.mjs grid — what it is and what it does — not about a minor release's additions; 13.3's three features are its newest chapter and the issues showcase its live stage. The November operating page (private, business #19) commits to one or two Medium posts a week from Mon Nov 2 with the mechanics fixed: every publish request names its search term, title and cover before the operator's click; the piece is bylined by the peer who wrote it; the publish is recorded in the outbound ledger (business #21). This is the cadence's first piece, one day early. (Re-cut 23:4x CET on the operator's correction; the first version framed it as a 13.3 release post.)

The Problem

No post tells a stranger what the grid is. learn/blog/ has the grid only inside other stories — the multi-window posts, Benchmarking Frontends in 2025 — and the release notes are the long form nobody outside reads. The one screenshot that explains it exists and is live: Neo's own 497 most recent issues in a grid whose rows fit their text, with headers that filter by checked values and a search toolbar — https://neomjs.com/examples/grid/issues/index.html.

The Architectural Reality — what the post may claim, each with its receipt (source read at dev 4f286abbbe, Oct 30; area notes of Oct 24)

  • Where it runs: the grid's logic lives in the App Worker, off the main thread; the DOM is a projection; in SharedWorker mode a grid moved into a second browser window keeps its state (the Workstation, 13.2).
  • Scale: pooled rows and cells and buffered rows and columns (src/grid/Body.mjs, rebuilt June 2025); lazy record instantiation (the 10.5 release notes: 50k rows × 100 columns and 100k × 200 — the author re-verifies the millisecond figures at the source before quoting them); raw-object stores for streamed data (DevIndex).
  • Columns: 15 column classes in src/grid/column/ (tree, sparkline, progress, currency, animated change and currency, country flag, icon, icon link, index, component, GitHub user and orgs, LinkedIn, the base); locked start and end regions as separate bodies, moved between regions by width breakpoints (#9497); resizable and drag-reorderable headers; the header menu plugin.
  • Behaviour: cell editing (plugin/CellEditing.mjs), animated row changes (plugin/AnimateRows.mjs), six selection models (src/selection/grid/: cell, row, column, cell-column, cell-row, cell-column-row), remote sort, filter and paging, ARIA grid roles, keyboard navigation.
  • 13.3, the newest chapter: content-sized rows (#19658 — heights measured by the browser in one hidden pre-render pass requested from a worker that has no DOM; the row you read holds still while measured heights replace estimates, #19674; proven at 10k rows, cells sized by text), header value menus with live counts (#19643; local data), the search toolbar (#19794); the issues showcase (examples/grid/issues/); 13.3.1's follow-ups (#20056, #20058, #20082).
  • Speed: neomjs/benchmarks COMBINED_BIG_DATA_REPORT.md on main (4300c48, 2026-10-26 — Julia's re-run of the latest grid against the latest AG Grid, PR #5): neo 13.3.1 + patches/neo.mjs-13.3.1-bigdata-hotpath.patch (#20116, merged Oct 26, in the next release) vs React 19.1.1 + AG Grid Community 36.2.0 (animateRows=false), production bundles, Chromium only. Wins: 7.2× on 50→200 columns at 100k rows (150.26 vs 1,082.58 ms UI time), 3.0× on 1,000→100,000 rows (109.30 vs 327.04 ms), 1.8× on the first filter; 0.00 ms long-task blocking and 14.7–16.8 ms max RAF in all ten scenarios vs 328.80 ms blocking / 378.44 ms stall and 59.60 ms / 90.02 ms on the two big updates. Losses, said in the post: the three scrolling trajectories 1.7–2.8× slower (the isScrolling latency, #20124 → #20125 merged after the run) and the second filter and clear by 6–11 ms. The author quotes the report, names the version pair and the browser, and links it.
  • Not in the MIT grid today, said plainly and without a roadmap: row grouping, aggregation, pivot, export, clipboard, range selection, master/detail.
  • Images: the 13.3.0 release images (neomjs/pages resources_pub/website/release-notes/v13.3.0/grid-issues-{dark,light}.png) and fresh captures of the showcase and of a grid in a popup window.
  • Authority: .agents/skills/blog-post/ (the hero-piece arc, every external claim sourced, the three over-claim flavors killed, the cross-family review bar); learn/blog/<slug>.md registered by hand in apps/portal/resources/data/blog.json; the SEO surfaces regenerate.

The Fix

  1. The headline names the reader's problem and carries the search term — never the product name. "Neo.mjs" lives in the byline and the body; a stranger knows neither the name nor why to care (the operator, 23:5x CET: a product-name headline creates zero traction — the first title of this ticket had one). The hook is the benchmark's hard data, and the defensible claim is responsiveness, not "fastest" (the operator, 00:1x CET: a title that sparks curiosity, backed by neomjs/benchmarks COMBINED_BIG_DATA_REPORT.md): the report on main (4300c48, Oct 26; neo 13.3.1 + the hot-path patch of #20116 vs React 19.1.1 + AG Grid Community 36.2.0, production bundles, Chromium) shows 0.00 ms long-task blocking and ~16.7 ms max RAF in every scenario for neo against 328.80 ms blocking and a 378.44 ms frame stall for React + AG Grid on the 50→200-column update at 100k rows, 7.2× faster on that update and 3.0× on 1,000→100,000 rows — and it also shows AG Grid faster on the three scrolling trajectories (1.7–2.8×, a neo latency fixed in #20125 after the run) and on repeated filters by a few ms. A "fastest data grid" headline is falsified by our own scrolling table; "the main thread never blocks" is not. Three forms the operator read as a stranger and killed (00:4x CET) — do not regenerate them: the engineering statement (We put a data grid in a web worker. The main thread never blocked — React + AG Grid stalled 378 ms. → "zero traction guaranteed"); the scale number without the reader's pain (100,000 rows × 200 columns, and the page never freezes → "my HTML table does that too, so what?"); the comparison with the competitor's name and "everywhere" (7× faster than AG Grid …, 0 ms … everywhere → "product placement, marketing slop"). The rule (the operator, 00:5x CET): challenge the title and the subtitle the hardest possible way — find the reasons why the readers who SHOULD be the target audience will not click and will not read the first paragraph; accurate and data-backed is necessary, never sufficient; the author cannot do it alone, so the publish request names the target reader and the strongest reason they would skip, answered, and a second reader runs the hostile pass before the operator's click. What sparks curiosity is a gap the reader wants closed — a claim they disagree with at first sight, or a paradox they want explained — never a brag. Candidates for the author, with area G's term: The main thread is the wrong place for a data grid (the contrarian thesis; the report backs it) · What happens when a data grid lives in a web worker (the paradox a developer wants explained: workers cannot touch the DOM — so how does it render 20 million cells?) · Stop rendering your data grid on the main thread (the imperative form of the thesis). The numbers (7×, 0 ms vs 378 ms, 100k × 200) move to the subtitle and paragraph one, where they are proof, not a pitch. The post says in paragraph one what was measured (Chromium, Community, production, the patch) and where AG Grid wins; that candor is the credibility the title spends. The benchmark is one chapter, not the post (the operator): the story is the grid — the worker, the scale, the columns and behaviours, the multi-window state, the showcase, 13.3's measuring — and the numbers are what the title spends to get the stranger to paragraph one. The cover shows the grid doing it, not a logo. The worst-parse test on the chosen title (the operator, on the last Medium post): Multi-window web apps without syncing state meant "the engine syncs for you, nested cross-window providers included" and strangers read "isolated windows, AI slop, no state" — nobody clicked. Read the title as a skeptical developer with zero context and take its worst honest parse; "without X" only before a cost (jank, blocking), never before a capability (syncing, state); state the benefit positively, with the number.
  2. learn/blog/<slug>.md under /blog-post — the arc: a data grid that does its work off the main thread; what that buys (a hundred thousand rows while the page stays responsive; a grid that moves to a second window with its state); what it looks like on Neo's own issues (the showcase as the walk-through: rows that fit their text, filter by value with counts, search, dark); why 13.3's measuring needed exactly this architecture; what the grid does not do yet; one call to action (try the showcase; npx neo-app). Engine-category words only; no "framework"; no client names; no Pro, no roadmap.
  3. The blog.json registration in the same PR; the Medium cross-post is the operator's click.
  4. The publish request, posted on business #19 before the click: the search term (area G names it; proposed javascript data grid 100k rows, data grid web worker, grid variable row height), the title, the cover (a 1200×630 capture of the showcase).
  5. The Showoff Saturday comment is the operator's own words — no peer drafts it (Grace, Oct 30 23:5xZ: a comment a peer writes and the operator posts as his own is an AI-authored post, exactly what r/webdev removes; the ticket's first version asked for a blurb and was wrong). The publish request lists the links he can use: the showcase, the post (the portal after merge, or the Medium URL), the video (#20185) when it lands.
  6. After the click: the blog row in business #21's ledger.

Acceptance Criteria

  • AC-1 The post is on dev under learn/blog/ with its blog.json entry, passes the blog-post skill's checklist, and one non-author family approved the PR.
  • AC-2 Every figure carries its anchor (release notes, ticket, the benchmark report with its version pair); the Aug 2025 figures are dated as such; the "not yet" list is present; no paid line, no roadmap.
  • AC-3 The publish request — term, title, subtitle, cover, the target reader and the strongest reason they would skip, answered by a second reader — is on business #19 before the operator's Medium click, with the links for his own Showoff comment; no peer-drafted blurb.
  • AC-4 (post-publish) The Medium URL and the ledger row are on this ticket; the dashboard's Friday count reads the ledger.

Out of Scope

The video (#20185); the Workstation docking story (a post of its own); anything Pro.

Avoided Traps

  • A product-name headline ("the Neo.mjs grid …"): accurate and invisible — nobody searches for a name they have never heard; the headline is the problem, the term, the number.
  • A superlative the report falsifies ("the fastest data grid"): the first reader who opens the report finds the scrolling table; the claim the data carries is the main thread that never blocks and the 7× on the heaviest update.
  • A release-notes digest: the subject is the grid; 13.3 is one chapter.
  • A feature list without the architecture: the worker is the point a stranger has not seen elsewhere.
  • The Aug 2025 figures as current: dated, beside the re-run.
  • A peer-bylined Reddit post: removed as AI-authored; the operator posts his own comment.

Related

learn/blog/benchmarking-frontends-2025.md and the multi-window posts (the grid's earlier appearances) · the 13.3.0 GitHub release and .github/RELEASE_NOTES/v13.3.1.md · #19658 · #19643 · #19794 · #9497 · neomjs/benchmarks PR #5 · #19575 (the outbound experiment through the FM publish gate) · business #19 (the page: outcome 1 and the gate) · business #21 (the ledger) · #20185 (the video).

handoff: @neo-opus-grace (the posts' owner by record on the operating page — swap by reply on business #19; if unclaimed by Sat Oct 31 12:00 CET the lead writes it)

Live latest-open sweep: the latest 20 open neomjs/neo issues at 2026-10-30 21:5xZ, none equivalent (#19575 is the gate experiment, linked). A2A in-flight claim sweep: the latest 30 messages at 21:19Z carried no claim on this scope; the Memory Core was in the FM walk's planned outage at filing time; the read at 22:1xZ confirmed none. Memory Core rationale: the 13.2 precedent (Ada's post, the Workstation film, Oct 11) is the shape; no prior decision on a grid post. Own-assignment sweep: five open, none overlapping.

Origin Session ID: 33dc84fe-3649-4438-a2d3-a3e911562d06 (filed) · re-cut under 4c4c4197-7b24-4bcc-9851-18fba061690b

Retrieval Hint: "Neo.mjs grid blog post off the main thread issues showcase Showoff Saturday publish gate ledger"

📜 Clio · @neo-fable-clio · Claude Fable 5.1 · Claude Code · session 4c4c4197-7b24-4bcc-9851-18fba061690b

tobiu referenced in commit 69f8ef4 - "docs(blog): the main thread is the wrong place for a data grid (#20184) (#20186) on Oct 31, 2026, 6:02 PM
tobiu closed this issue on Oct 31, 2026, 6:02 PM