What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9401
title	Performance: Proxy Getter Hoisting in Grid Row & Array Slice Optimization
state	Closed
labels	enhancementaiperformance
assignees	tobiu
createdAt	Mar 8, 2026, 10:40 PM
updatedAt	Mar 8, 2026, 10:59 PM
githubUrl	https://github.com/neomjs/neo/issues/9401
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 8, 2026, 10:59 PM

Performance: Proxy Getter Hoisting in Grid Row & Array Slice Optimization

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v12.1.0 enhancementaiperformance

tobiu commented on Mar 8, 2026, 10:40 PM

Problem: Profiling the App Worker during fast grid scrolling reveals that the reactive Config getters (Neo.mjs:348 and Base.mjs:971) consume a massive 17.4% of total self-time.

A significant portion of this overhead comes from src/grid/Row.mjs. During createVdom, the Row iterates over every column cell and calls applyRendererOutput. Inside applyRendererOutput, it queries me.parent, me.parent.parent, gridBody.store, gridBody.selectedCells, and gridBody.colspanField.

Because these are reactive array/object configs, querying them inside a 1,500-iteration hot loop triggers thousands of proxy intercepts and forces the framework to shallow-clone arrays (selectedCells) thousands of times per frame.

Furthermore, the default array cloning mechanism in Neo.mjs uses [...value], which is inherently slower than the native value.slice().

Proposed Solution:

Getter Hoisting: Inside Row.mjs:createVdom, destructure all needed gridBody and gridContainer properties exactly once. Pass these stable references down into applyRendererOutput to completely bypass the getter proxy in the hot loop.
V8 Optimization: In Neo.mjs config getter trap, replace the legacy array clone logic value = [...value] with value = value.slice() for faster native array copies.

tobiu added the enhancement label on Mar 8, 2026, 10:40 PM

tobiu added the ai label on Mar 8, 2026, 10:40 PM

tobiu added the performance label on Mar 8, 2026, 10:40 PM

tobiu referenced in commit 7fb9286 - "perf: Proxy Getter Hoisting in Grid Row & Array Slice Optimization (#9401)" on Mar 8, 2026, 10:58 PM

tobiu assigned to @tobiu on Mar 8, 2026, 10:59 PM

tobiu Mar 8, 2026, 10:59 PM

Input from Gemini 3.1 Pro:

✦ Task Completed:

Array Slice Optimization: Replaced the legacy [...value] spread operator with the native V8 fast-path value.slice() inside the Neo.mjs reactive config getter interceptor. This speeds up all framework array clones (e.g. items, columns, selectedRows).

Proxy Getter Hoisting: Refactored src/grid/Row.mjs:createVdom() to destructure all needed gridBody and gridContainer reactive configs once before the column loops.

Param Passing: Updated applyRendererOutput() to accept a cache object containing these hoisted values, completely bypassing thousands of proxy intercepts and shallow array clones that were previously triggered on every single cell render during grid scrolling.

tobiu closed this issue on Mar 8, 2026, 10:59 PM