Your own engine?! Wow, that's incredible. Is this gonna be like Servo where people can build a browser around this, or will it be a standalone browser?
I recently switched from Arc to Helium but it's still Chrome with different paint. When I was using Opera 12, it was the most standards-compliant browser so it became my main. What are the goals for cwbrowser (and is the name permanent)?
Modern browsers should no longer score 100 on Acid 3 though.
>By April 2017, the updated specifications had diverged from the test such that the latest versions of Google Chrome, Safari and Mozilla Firefox no longer pass the test as written
Yes, but considering the goal of his project is a proof of concept, that is, proving this project is possible, acid3 is a good place to start to prove the worth of the project and aiming 100% first make more sense. Tweaks will be needed one way or another to make it equivalent to the big 3.
https://github.com/web-platform-tests/wpt/commits/master/aci... shows the history of the web-platform-tests copy of WPT, which has mostly followed Hixie’s earlier updates to Acid3 by simply commenting out assertions that no longer match what specs say.
For reference, Safari is doing around 53, and Chrome is around 60 for M5, of which they were bragging about [0]. So curious to see whether there's any gains from your custom browser.
i'm assuming this is written with LLMs given the writing on that page and the nature of the other "products" on that website. i would not call that hand-written, as the page does in the second paragraph
I did use LLM for the landing page since I don't have much time on it. The browser however not that much. I did use claude and my own cwcode to help developing this, but a lot of times the zig code had to be written by hand. Hope this answered your question.
Cursor was lambasted from the start because they wrote blog posts about writing a browner “from scratch in rust” but it was neither without dependencies nor actually worked.
It was not serious engineering. It was a side project experiment with yeeting tokens into the sun.
Also, using an agentic framework and writing code by hand "a lot of the time" does not count as "from scratch".
[1] https://news.ycombinator.com/item?id=49129191
I’d love to see something entirely FOSS dethrone the big corp browsers, hope that’s the goal here.
I recently switched from Arc to Helium but it's still Chrome with different paint. When I was using Opera 12, it was the most standards-compliant browser so it became my main. What are the goals for cwbrowser (and is the name permanent)?
- how exactly do you go about writing your own browser engine
- what specs are you supposed to follow
- how do you measure or determine if your browser engine is compliant
- how long do you think such a task would take (no AI / with AI)
- how do you test something like this?
>By April 2017, the updated specifications had diverged from the test such that the latest versions of Google Chrome, Safari and Mozilla Firefox no longer pass the test as written
[0]: https://browserbench.org/Speedometer3.1/
[0]: https://blog.google/chromium/a-double-victory-for-web-speed-...
Do you have WPT tests results, and/or screenshots of it rendering real websites?
Eh.
what's the deal with that? why is Google Drive zips your main distribution method, with no source available?
and finally: are you going to change this?
It was not serious engineering. It was a side project experiment with yeeting tokens into the sun.