Show HN: I worked on a new browser for 2 years, today it passed Acid 3
code.intellios.ai
code.intellios.ai
Also, using an agentic framework and writing code by hand "a lot of the time" does not count as "from scratch".
Working with an agentic framework for more than a week make me want to throw it over the cliff
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.
>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
But is that what happened? If you pass tests that conflict with the specs, then that implies that the implementation is not based on specs, but on feedback from the test. Which means it may be designed to pass the test, and not much good once you go outside the test examples.
I'll extend the benefit of the doubt and say that it's possible that the implementation is based on an older version of specs, one that matches the tests. But it doesn't inspire confidence that all we're shown is a single screenshot and no source code.
I’d love to see something entirely FOSS dethrone the big corp browsers, hope that’s the goal here.
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 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)?
[0]: https://blog.google/chromium/a-double-victory-for-web-speed-...
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?
What license will you release under?
Do you have WPT tests results, and/or screenshots of it rendering real websites?
Eh.
It was not serious engineering. It was a side project experiment with yeeting tokens into the sun.