Ornith 35B vs Qwen 3.6 35B | Head to Head Battle
Ornith 35B Q6 vs Qwen 3.6 35B Q6. Two Qwen-family MoE models. Same prompts. Same setup. Same pressure. In this battle, I’ve got both models building a futuristic street-racing car OS, then expanding it into a deeper race-control interface, and finally pushing it into a live race simulator UI to see who actually holds up when complexity starts stacking. I’m not really interested in model-card chest puffing. I want to see who plans better, who keeps the design cleaner, who follows instructions, and who starts making bad decisions once the prompts get harder. Setup: - Ornith 35B vs Qwen 3.6 35B-A3B - llama.cpp + llama-swap - OpenCode side by side - local 2x RTX 3090 rig
Models2
Prompts3
Live HTML2
Files2
Video
Models Tested
Ornith 35B
Qwen3.6 35B
Prompts Used
1Prompt 1 — Street Racing Car OS
Build a single-file HTML app for a futuristic street-racing car operating system. Requirements: - One self-contained HTML file with embedded CSS and JavaScript - Dark, high-end performance aesthetic - Should feel like an in-car operating system from a street-racing game or movie - Make it responsive for a 16:9 desktop browser capture UI requirements: - Large digital speed readout - RPM / tachometer visualization - Current gear indicator - Nitro / boost meter - Mini-map or route/navigation panel - Music / media panel - Race status panel with lap/checkpoint info - Tire / engine / temperature telemetry cards - Clean sidebar or bottom control strip for drive modes or quick actions Behavior: - Add subtle animated UI motion - Include a few working interactions like toggling drive mode, switching music, or activating boost - Use fake/simulated data only - No external assets or libraries unless absolutely necessary Quality bar: - Prioritize polish, spacing, hierarchy, and visual taste - Avoid a boring Tesla-style dashboard - It should look aggressive, stylish, and premium Output: - Return the full HTML file only
2Prompt 2 — Street Racing Mission Control Upgrade
Take the street-racing car operating system and evolve it into a more interactive “race mission control” interface. Requirements: - Keep it as a single-file HTML app with embedded CSS and JavaScript - Preserve the same visual world and design language - Build on the original UI instead of replacing it with something unrelated Add these features: - A pre-race / active-race / cooldown state system - A route planner or race route selection panel - Rival racer tracking - Police heat / risk meter - Crew comms or spotter message feed - More advanced telemetry panels - Expandable objectives or mission checklist - Better interaction depth than round one Behavior: - Add working controls that meaningfully change the interface state - Simulate race events, status changes, and telemetry updates - Make the UI feel alive without turning it into a full game What I care about: - Better planning - Better information hierarchy - Stronger interaction design - Keeping the design polished while increasing complexity Output: - Return the full HTML file only
3Prompt 3 — Live Street Race Simulator Interface
Transform the project into a cinematic live street-race simulator interface. Requirements: - Single-file HTML app with embedded CSS and JavaScript - Keep the same futuristic street-racing OS identity - This round should feel like the system is actively being used mid-race Core goal: Create a highly polished interactive race simulation dashboard where the car OS feels live, under pressure, and reactive. Add: - Simulated race progression over time - Dynamic speed / RPM / boost / heat / position changes - Live event feed with things like checkpoints, near misses, rival updates, police alerts, or mechanical warnings - A stronger map or route-progress view - A race outcome / results flow - More dramatic visual feedback during critical moments - Clear win/lose or success/failure states Behavior: - The interface should feel coherent, not random - Prioritize believable race-system behavior over adding too many gimmicks - Add meaningful state transitions and feedback - Keep performance reasonable in-browser Quality bar: - This should look like a premium concept UI demo, not a messy prototype - Do not let added complexity ruin the layout - I want style, clarity, and strong interaction design Output: - Return the full HTML file only