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
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
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.
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)?
Acid3 is 100 tests but to have a browser that works on any real percentage of the internet you need to pass the over 52000 tests and nearly two million subtests [1] that make up the Web Platform Tests [2]
This is like the difference between a college degree and passing a spelling test.
Congrats! Even if this is vibecoded, this is a hard task to get just a barebones renderer working.
I do concur with the few other folks here that the ShowHN is meant for actually showcasing something rather than the landing page with a screenshot. I would expect it to link to a downloadable binary or the source.
Showcasing Web Platform Tests coverage would be better than just Acid 3.
For anyone else wondering why this is hard: I'm writing a browser engine that renders to png. I dug into the source code of other browser engines and came across scenarios that I had never imagined. I learnt about font rasterization, execution contexts for scripts, etc. There's a tonne of stuff to be learnt by building something like this.
Supporting iframes and each group of the web platform APIs, each add another layer of complexity that I definitely dont want to be tackling as a solo dev.
I was wondering if you could add a Acid2 rendering screenshot to the site, please? It tests some different things than Acid3, so I'm curious how it fares.
32 comments
[ 0.28 ms ] story [ 18.0 ms ] thread[0]: https://browserbench.org/Speedometer3.1/
>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
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)?
Do you have WPT tests results, and/or screenshots of it rendering real websites?
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
Eh.
https://news.ycombinator.com/showhn.html
This is like the difference between a college degree and passing a spelling test.
1. https://servo.org/blog/2023/07/20/servo-web-platform-tests/ 2. https://github.com/web-platform-tests/wpt
Not to mention this site is clearly vibe coded and has a vague call to action and no source code available thus indicating possible vaporware.
What license will you release under?
I do concur with the few other folks here that the ShowHN is meant for actually showcasing something rather than the landing page with a screenshot. I would expect it to link to a downloadable binary or the source.
Showcasing Web Platform Tests coverage would be better than just Acid 3.
For anyone else wondering why this is hard: I'm writing a browser engine that renders to png. I dug into the source code of other browser engines and came across scenarios that I had never imagined. I learnt about font rasterization, execution contexts for scripts, etc. There's a tonne of stuff to be learnt by building something like this.
Supporting iframes and each group of the web platform APIs, each add another layer of complexity that I definitely dont want to be tackling as a solo dev.