Comment by Uehreka

2 hours ago

I feel like I’ve unlocked a magic cheat code here, everyone listen up:

I read that GasTown post, thought it was cool, pulled it down, found out the principles are there but the implementation is still a little glitchy, took a couple IDEAS from Gas Town (beads and the idea of controlling an agent with hooks and tmux), made a small ralph-wiggum-loop-ish thing, and I’m now building my 4th (this is not a joke) Acid3-compliant browser this week (Acid3 doesn’t include HTML5, so this is a large but not unreasonable project).

And I did it all without investing a dime in any crypto, or telling anyone to do so (for the record: stay in school kids, don’t invest in crypto). I have somehow achieved all of the upside with none of the downside. Study me. I’ve clearly figured out something that has eluded all of these pump-and-dump callout bloggers.

Why don’t you do something useful with your superpowers?

  • In the past year I’ve used AI coding assistants on a life-saving medical device product (no, followup commenter, I did not ship unreviewed vibes in a medical device product), a tool for editing documentation used in healthcare (no, followup commenter, it does not use LLMs to generate documentation), a piece of custom cue calling software for theater and to reverse engineer a TCP protocol to help modernize a piece of water quality measuring equipment.

    But hey, every once in a while I like to have a little fun ;)

    • Yeah none of those are nearly ambitious enough for someone who is spitting out browsers in less than a full workday.

      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?

      2 replies →

I'm going to fucking crash out if another person says they're making a browser and their inline layout does this shit[1] I swear to god.

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

[2] https://drafts.csswg.org/css-inline-3/

[3] https://drafts.csswg.org/css-text-3/#boundary-shaping

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