Validation
Planned
ROSETTA 21 — Implementation Comparison
Compare defensive validation and fallback behavior across languages.
Rosetta Stone Validation
Accept valid input and return safe controlled output for invalid input.
Accept valid input and return safe controlled output for invalid input.
Objective & Comparison Rule
Build each implementation without changing the shared behavior or visual target.Objective
Compare defensive validation and fallback behavior across languages.
Comparison Rule
Accept valid input and return safe controlled output for invalid input.
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.Technologies
Build Instructions
Start with the first technology listed under Technologies, then reproduce the same behavior in each following implementation.Accept valid input and return safe controlled output for invalid input.
Build and run the initial implementation, then save the visible expected result.
Compare syntax, typing, modules, runtime, standard library, data handling, and implementation size.
TypeScript Implementation Reference
This implementation becomes the first concrete Rosetta comparison point.function parseMetadata(value: unknown): Record<string, unknown> {
try {
const parsed = JSON.parse(String(value));
return parsed && typeof parsed === "object" && !Array.isArray(parsed)
? parsed
: {};
} catch {
return {};
}
}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.- 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