Turtle – Web Browser written from scratch for 2 years

Turtle is a macOS web browser whose rendering engine — HTML parser, CSS cascade, layout and paint — is written completely from scratch in Zig, with Google

I've posted this game here before, hopefully a repost is fine as the game has changed quite a bit (improved AI, improved mapeditor, much quicker gameplay, etc). Game is based on JavaScript/Canvas and WebSockets. On the browser side the map is pre-rendered (as a background image), just the mobile units/buildings and animations are dynamically rendered. The lobby server is made in node.js, but the game server is C++ for performance reasons (mainly the pathfinding). I found the C++ WebSocket libraries out there to be too difficult to use so I made my own based on the rfc. Overall I…

Hi HN! Thanks for your attention to my post. It was a big challenge to run most of Node.js packages in browser, fast moreover. Virtual File system, resolve import/export. I got cold many times, depressions, burned out, yet still alive and finished it. Many guys helped me with an advice. Many users give a lot of positive feedback. There are 200,000 monthly unique users. I work full time now because of the freemium business model. To be honest - I am happy after many years of hard work.

Hi HN! Korean high school senior here, about to start CS in college. I built a browser engine from scratch in C++ to understand how browsers work. First time using C++, 8 weeks of development, lots of debugging—but it works! Features: - HTML parsing with error correction - CSS cascade and inheritance - Block/inline layout engine - Async image loading + caching - Link navigation + history Hardest parts: - String parsing(html, css) - Rendering - Image Caching & Layout Reflowing What I learned (beyond code): - Systematic debugging is crucial - Ship with known bugs rather than chase…

I've been working on browser automation infrastructure for a while and kept hitting the same ceiling: Playwright and Puppeteer are great for scripting but fall apart when you need stealth at scale. Cloud-based solutions like Browserbase work but you're sending all your data to a third party and can't control the environment. So we built Owl Browser, a self-hosted Chromium-based engine that runs in a single Docker container. The core technical problem we tried to solve was fingerprint consistency. Most browser automation tools either ignore fingerprinting entirely or apply surface-level…

Try it at: ssh krnl.duetbrowser.com No sign up, totally free - no download. Let me know what you think. Prior art exists (brow.sh) but I wasn't satisfied with their graphical take. I wanted the raw, old skool terminal days of the early internet - BBS, and old green phosphor library comptuers - but running the modern web, with all the bells and jingle jangle whistles (JavaScript, etc). No funding, no VC, just 100% raw terminal fun. Not sure how long the demo will last, but try it out.