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	7033
title	Feature: Add Neo.mjs vs. Angular Comparison Article
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Jul 13, 2025, 12:15 AM
updatedAt	Jul 13, 2025, 12:17 AM
githubUrl	https://github.com/neomjs/neo/issues/7033
author	tobiu
commentsCount	0
parentIssue	7029
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jul 13, 2025, 12:17 AM

Feature: Add Neo.mjs vs. Angular Comparison Article

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

Closed v10.0.0-beta.6 enhancement

tobiu commented on Jul 13, 2025, 12:15 AM

Is your feature request related to a problem? Please describe. Developers evaluating or learning Neo.mjs often come from other established frameworks, including Angular. There is a need for a clear, concise comparison that bridges their existing knowledge to Neo.mjs concepts and highlights Neo.mjs's unique advantages.

Describe the solution you'd like Add a new article within the learn/comparisons directory comparing Neo.mjs with Angular. The article should:

Bridge Knowledge Gaps: Explain how concepts familiar from Angular (e.g., modules, components, services, dependency injection, RxJS) map to Neo.mjs.
Highlight Differentiators: Clearly articulate Neo.mjs's unique selling points (e.g., worker-based architecture, fine-grained reactivity, Main Thread responsiveness, VDOM approach, batching/aggregation, zero-build dev mode, batteries-included) in contrast to Angular.
Provide Side-by-Side Analysis: Use structured sections to compare key aspects like architecture, rendering mechanism, component model, state management, build process, and dependency management.
Discuss Trade-offs: Acknowledge any trade-offs or scenarios where one framework might be preferred over another.
Suggest Use Cases: Guide developers on when Neo.mjs might be the optimal choice, particularly emphasizing its technical superiority in areas like Main Thread responsiveness and performance under heavy load.

Describe alternatives you've considered (None considered, as this is the proposed solution.)

Additional context This article will be crucial for attracting Angular developers to Neo.mjs, enhancing discoverability, and positioning Neo.mjs as a technically superior alternative for specific use cases.

Affected Files (Conceptual):

learn/comparisons/NeoVsAngular.md (new file)
learn/comparisons/Overview.md (will be updated to include this link)

tobiu assigned to @tobiu on Jul 13, 2025, 12:15 AM

tobiu added the enhancement label on Jul 13, 2025, 12:15 AM

tobiu added parent issue #7029 on Jul 13, 2025, 12:15 AM

tobiu referenced in commit a1b35b9 - "Feature: Add Neo.mjs vs. Angular Comparison Article #7033" on Jul 13, 2025, 12:17 AM

tobiu closed this issue on Jul 13, 2025, 12:17 AM