Nested Data

ROSETTA STONE

Planned

ROSETTA 04 — Implementation Comparison
Compare nested record structures across languages.

Rosetta Stone Nested Data Preview coming soon

ROSETTA 04

Rosetta Stone Nested Data

Comparison Contract

Nested objects, classes, dictionaries, lists, and property access.

Comparison Contract

Nested objects, classes, dictionaries, lists, and property access.

Objective & Comparison Rule

Build each implementation without changing the shared behavior or visual target.

Rosetta Contract

Objective

Compare nested record structures across languages.

Comparison Rule

Nested objects, classes, dictionaries, lists, and property access.

Keep equivalent input, behavior, and visible output in every later language version.

Implementation Plan

Keep the comparison surface fixed while language syntax and runtime details change.

Structure

project/
├── input/
│   └── fixture.json
├── expected/
│   └── output.json
├── package.json
├── tsconfig.json
├── index.html
├── styles.css
└── src/
    └── app.ts

Initial Implementation

JavaScript / modern ECMAScript
HTML
CSS
JSON

Comparison Languages

JavaScript / modern ECMAScript
TypeScript
Angular
Python
Java
C#
PHP

Source Learning Project

Source Learning Project — TypeScript Lab: Nested Object Inspector

src/datastore/types.ts

Technologies

JavaScript / modern ECMAScript

TypeScript

Angular

Python

Java

PHP

Build Instructions

Start with the first technology listed under Technologies, then reproduce the same behavior in each following implementation.

Freeze the Contract

Define the exact input, visible behavior, and expected output.

Build Initial Implementation

Implement the reference version with the same standalone visual layer.

Later Comparison

Rebuild without changing the contract.

TypeScript Implementation Reference

This implementation becomes the first concrete Rosetta comparison point.

Reference Code

Use the same input when building later language versions.

interface Technology { name: string }
interface Project {
  title: string;
  technologies: Technology[];
}

const project: Project = {
  title: "Sandbox",
  technologies: [{ name: "TypeScript" }],
};

TypeScript Implementation Configuration

Keep the TypeScript implementation independently buildable; each implementation should keep its own required setup.

package.json

{
  "type": "module",
  "scripts": { "build": "tsc" },
  "devDependencies": { "typescript": "^7.0.2" }
}

tsconfig.json

{
  "compilerOptions": {
    "rootDir": "./src",
    "outDir": "./dist",
    "target": "ES2022",
    "module": "ES2022",
    "lib": ["ES2022", "DOM"],
    "strict": true,
    "sourceMap": true
  },
  "include": ["src/**/*.ts"]
}

Comparison Dimensions

Record differences that teach language and runtime behavior rather than cosmetic syntax.

Compare

Syntax and data declarations
Typing and validation
Collections and standard-library operations
Modules and file organization
Runtime and build requirements
Database or HTTP APIs when applicable
Visible output and behavioral equivalence