Group By Category
Planned
ROSETTA 07 — Implementation Comparison
Compare grouping algorithms using the same project data.
Rosetta Stone Group By Category
Build keyed groups from repeated category values and render grouped results.
Build keyed groups from repeated category values and render grouped results.
Objective & Comparison Rule
Build each implementation without changing the shared behavior or visual target.Objective
Compare grouping algorithms using the same project data.
Comparison Rule
Build keyed groups from repeated category values and render grouped results.
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.Build keyed groups from repeated category values and render grouped results.
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.const groups = new Map<string, Project[]>();
for (const project of projects) {
const key = project.category;
const group = groups.get(key) ?? [];
group.push(project);
groups.set(key, group);
}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