Alex Kanunnikov

Question: give me contradictions in this documentation.

@sukima looks like some error in implementation, Benchmark is unable to start: check on ``` http://localhost:5173/benchmark ``` seems reactive tests is breaking ``` http://localhost:5173/tests.html?filter=reactive ```

@sukima thanks! Going to update PR. GH says your invite is still pending:

[artifact-1.pdf](https://github.com/lifeart/glimmer-next/files/15384909/artifact-1.pdf)

@sukima seems this signals implementation is way better at least in `unwatch` performance. Some floating in numbers may be caused by increased memory usage (GC).

```typescript // src/utils/context.ts import { registerDestructor } from './glimmer/destroyable'; import { Component, RENDER_TREE } from './shared'; const CONTEXTS = new WeakMap(); export function getContext(ctx: Component, key: symbol): T | undefined...

## Context API: Sharing Data Across Components GXT's Context API provides a mechanism for sharing data across components without explicitly passing props through every level of the component tree. This...

we should not reuse tags if used inside control flow (`if`) - https://github.com/lifeart/glimmer-next/pull/149

Comparing to existing [Lamport clocks](https://v5.chriskrycho.com/journal/autotracking-elegant-dx-via-cutting-edge-cs/) model in [GlimmerVM](https://gist.github.com/pzuraq/79bf862e0f8cd9521b79c4b6eccdc4f9) we eliminate tag re-validation phase, and literally executing only values needs to be updated. Benefits comparing to Lamport clock - is: -...

## Reactivity in GXT: A Simplified Approach GXT introduces a streamlined reactivity system inspired by Glimmer's `@tracked` but with a focus on explicit DOM updates and minimal overhead. This system...