I held off on commenting on the last AI browser post because the author said "it's not even good" so they recognized it's trash (it was).
Please educate yourself on how inline layout is supposed to work[2] first. (no, you cannot lay out text span-by-span[3] either...)
[1] https://github.com/chrisuehlinger/viberowser/blob/df6f4a265a...
Where can I find the Go version?
Please stop using Acid3 as some holy grail that lets you say you built a browser.
I have no idea how/if this passes Acid3 but this is not inline layout.
Your browser does not have the concept of breaking a line once it gets too long[1].
Your browser does not even shape text during layout and it renders text using a DrawString[2] function from a library that only applies kerning. No complex shaping to be seen in a light-year radius.
There is no trace of bidi-reordering either. I can't link to anything here since there's nothing to link to.
I will leave this[3] here too but I'm not going to draw conclusions without a deeper understanding of wtf the agent did here and how Acid3 works.
From now on if you still don't understand how this does not deserve the title of a browser I will assume you are trolling.
> I’m not going around telling people to download or use these things.
My problem is that you're telling people you built a browser. Some people have standards for what can be considered even a "toy" browser (this is not it).
[1] https://github.com/chrisuehlinger/viberowser-go/blob/93f2638...
[2] https://cs.opensource.google/go/x/image/+/refs/tags/v0.35.0:...
[3] https://github.com/chrisuehlinger/viberowser-go/blob/93f2638...
But hey, every once in a while I like to have a little fun ;)
This is at least a 100x speed up. You should be cranking out operating systems in a few days. Why haven’t you built an integrated OS, programming language, browser, and game engine yet?
I will of course be complaining vehemently on HN whenever someone’s website fails to render properly in my janky obscure browser, as is tradition.