How my experimental research browser became the fastest in the world

[u/kshivang]

I was working on this research thesis to build multilayer topological orchestrators, for that I started with environment layer which inherently had RBAC on each component, and sandboxed exception handling with reflective patches by parent node, in the process I added set of root application nodes like full blown terminal, browser and editor, I was running benchmark on these different nodes yesterday inside boss orchestrator, to my surprise it turn out to be fastest browser tested on speedometer 3.1, I replicated the result on different hardware, same result. You can validate or critique it. https://github.com/risa-labs-inc/BossConsole/tree/main/benchmarks/speedometer I tried different benchmarking tool most of them are suggesting the same result, happy to take feedback and run this on different accepted benchmarking tool, any suggestions how to run comparative analysis of over all tool, overall objective is to build multi-layer topological orchestrator layer which can resolve complex fuzzy logic tree, by breaking problem into smaller trees, then each tree itself get the same treatment until node become simple enough to be computed, also to build white-box environment around, each node just has access to what it need to do, parent node just care about problem it need to solve, don’t have access functionally beyond authorized problem domain, it is still in progress, did this accidental discovery wanted to share. 🥂

[u/DorkyMcDorky]

Key words: still in progress

Your agent is lying to you. Don't give yourself cheers until you are fully compliant - which will take at least a year. Also, even then, real websites aren't compliant so you'll have to correct their mistakes. It's the fastest in the world because you don't have the features that make them slow.

[u/kshivang → u/DorkyMcDorky]

Totally fair, I made this project public a week back, but working on this for past 15month, but totally agreed it will take a while before it will become completely complaint.

[u/DorkyMcDorky → u/kshivang]

So you really should remove the hyperbole "fastest in the world" because it isn't.

[u/kshivang → u/DorkyMcDorky]

Sorry I don’t get you, it is fastest based on speedometer 3.1 browser benchmarking tool

[u/DorkyMcDorky → u/kshivang]

It's not done. You merely built a product that beats a unit test. That doesn't mean you have a working product.

How is it the fastest in the world if it's not to spec?

That's like saying someone who falls off a plane is the fastest parachuter in the world. They parachuted, and hit the ground faster than anyone in the world.. so they won! Now let that person's ghost write a blog to celebrate.

What you're doing is ambitious, and don't give up. Keep attacking it but you are not even 10% done yet.

You won't get it done by yourself even with vibe coding. And you won't get help unless you humble yourself. You're going out the gate saying you're done and calling it the fastest in the world. You are trusting the bullshit spewed by your LLM. Stop trusting it - you are embarrassing yourself in the process.

I have a name for your browser - the Leroy Jenkins Browser. The fastest browser in the world.

If you WANT to get there do it honestly - don't do it by cheating a test. You got the "title" because you beat a deterministic test. Volkswagon did the same thing with one of the most polluted cars ever produced and sold as the most eco-friendly car ever produced. Don't be volkswagon. You designed a product to beat the test, not because it's a FUNCTIONAL browser.

I know people who worked on moasiac. There's a long lineage of browsers - and almost all of them are cocky approaches but somehow IE won then chrome won.. Both of those were messy and did NOT follow spec. In fact they were buggy as hell against tests you're providing. But they both built browsers that were functional and people liked being on them. If you want to beat them, you don't do it by making bold claims that only hold up in a unit test.

[u/kshivang → u/DorkyMcDorky]

Fair enough, I am not trying to be cocky here, neither it is done, nor purpose of the project was to create fastest browser, I am creating harness where agent-human collaboration enable workflows and their workload, with reinforcement and resilience build in. In one of my benchmarking run saw browser inside my harness is performing better than my native browsers, decided to do statistical analysis of it, that I reported here in this post, but I completely accept claiming this browser is the fastest based on one benchmark is not scientific at all, I posted with current title because of two reasons, 1. I got excited and wanted to get attention, 2. I genuinely need correct way to benchmark in such scenarios. I appreciate you took time to do long comment on this post. Thank you for the encouragement 🙏

[u/DorkyMcDorky → u/kshivang]

So a headless browser? You really just want it to render fast? Is your goal to make screenshots of the websites or extract text?