[Uehreka]

You found it! Yeah the 4th version of the browser is in Haskell and is only a couple hours in, so it’s nowhere near done. The Go version achieved Acid3 compliance in 7 hours, but I expect this one to take a lot longer since Haskell is a bit more difficult to work with and there’s probably less Haskell in the training dataset.

[afishhh]

> The Go version

Where can I find the Go version?

[Uehreka]

I’d been archiving/scrubbing each one so that the next assistant wouldn’t be able to use the previous branch as a guide, but since you asked, I pushed the archive of the Go one, feel free to rip it apart: https://github.com/chrisuehlinger/viberowser-go

[afishhh]

https://github.com/chrisuehlinger/viberowser-go/blob/93f2638...

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.

[Uehreka]

So I called out Acid3 in the original comment (and mentioned why it’s not the holy grail) so people wouldn’t get the idea that I was building full-on modern browsers. I’m not sure what I need to say to make y’all happy. I’m just excited that these tools are capable of doing non-trivial work and I’m having fun throwing tasks at it to see what comes out. I’m not going around telling people to download or use these things.

[afishhh]

Brother.

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...

[malfist]

It's easy to have acid 3 compliance if your acid 3 compliance test is printing 100/100 and then checking to see if 100/100 was printed