Brian Cardarella
@bcardarella.bsky.social
CEO of DockYard
Sailor
Creator of LiveView Native
twitch.tv/bcardarella
Sailor
Creator of LiveView Native
twitch.tv/bcardarella
oh that's dope
February 16, 2026 at 8:43 PM
oh that's dope
Is this the MUD (I think?, maybe MMORPG?) you were referencing in the past?
February 16, 2026 at 8:34 PM
Is this the MUD (I think?, maybe MMORPG?) you were referencing in the past?
We have that mostly working with Lighpanda but unfortunately their license is AGPL. They were nice enough to offer us an alternate license but after researching dual license projects it felt too risky to commit to that.
February 15, 2026 at 8:14 PM
We have that mostly working with Lighpanda but unfortunately their license is AGPL. They were nice enough to offer us an alternate license but after researching dual license projects it felt too risky to commit to that.
no, it's just spread out on different repos. The SwiftUI client is on a branch of the former LiveVeiw Native SwiftUI client. It's still in "spiking this all out" mode.
February 15, 2026 at 8:14 PM
no, it's just spread out on different repos. The SwiftUI client is on a branch of the former LiveVeiw Native SwiftUI client. It's still in "spiking this all out" mode.
but still pursuing the idea of what LVN was intended to be, just in a more generic way and unfortunately it won't work with LiveView because of the architectural limits that ultimately lead to LVN's demise
February 15, 2026 at 7:52 PM
but still pursuing the idea of what LVN was intended to be, just in a more generic way and unfortunately it won't work with LiveView because of the architectural limits that ultimately lead to LVN's demise
yeah this was announced a while back
February 15, 2026 at 7:51 PM
yeah this was announced a while back
Then all DOM CRUD operations will be communicated and sync'd with the native UI framework's view tree.
February 15, 2026 at 7:50 PM
Then all DOM CRUD operations will be communicated and sync'd with the native UI framework's view tree.
I'm skipping the rendering part for that very reason, as I'm not building it to be used as a replacement for Chrome, Safari, etc...
As you speculated, we plug in the native UI framework and delegate rendering to that. The browser will maintain DOM state and run JS on that DOM.
As you speculated, we plug in the native UI framework and delegate rendering to that. The browser will maintain DOM state and run JS on that DOM.
February 15, 2026 at 7:50 PM
I'm skipping the rendering part for that very reason, as I'm not building it to be used as a replacement for Chrome, Safari, etc...
As you speculated, we plug in the native UI framework and delegate rendering to that. The browser will maintain DOM state and run JS on that DOM.
As you speculated, we plug in the native UI framework and delegate rendering to that. The browser will maintain DOM state and run JS on that DOM.
All of this has motivated me to implement these tools and needs outside of the browser work. So I've mostly paused for the month while I work on these tools with the hope/goal it will solve those needs when I restart in a few weeks.
We'll see.
We'll see.
February 15, 2026 at 6:58 PM
All of this has motivated me to implement these tools and needs outside of the browser work. So I've mostly paused for the month while I work on these tools with the hope/goal it will solve those needs when I restart in a few weeks.
We'll see.
We'll see.
Then the lost knowledge of what the agent may learn then forget during compaction or new sessions.
February 15, 2026 at 6:58 PM
Then the lost knowledge of what the agent may learn then forget during compaction or new sessions.
I've also found that the tools using by AI agents right now to be very costly for huge projects. Making tool calls for writing code that just output IO may seem fast for small projects but really slow down at scale.
February 15, 2026 at 6:58 PM
I've also found that the tools using by AI agents right now to be very costly for huge projects. Making tool calls for writing code that just output IO may seem fast for small projects but really slow down at scale.
But the bigger issue is just context window limits. I found that with features that had overlapping internal architectural needs, the AI would implement both features in a unique way, not leveraging what was already written because it was too costly to the model to find it in the project.
February 15, 2026 at 6:58 PM
But the bigger issue is just context window limits. I found that with features that had overlapping internal architectural needs, the AI would implement both features in a unique way, not leveraging what was already written because it was too costly to the model to find it in the project.
I have hit significant limits on how well AI models can do this work. Mostly it comes down to the project size. I have found that the AI models write Zig very well, perhaps there are quality issues that someone could find but I'm less concerned as long as tests are passing and performance is there.
February 15, 2026 at 6:58 PM
I have hit significant limits on how well AI models can do this work. Mostly it comes down to the project size. I have found that the AI models write Zig very well, perhaps there are quality issues that someone could find but I'm less concerned as long as tests are passing and performance is there.
Then there are zero compromising and comprehensive platform tests to build towards.
So on that end I feel confident as I progress and am getting more of WPT to pass that this is the right path.
So on that end I feel confident as I progress and am getting more of WPT to pass that this is the right path.
February 15, 2026 at 6:58 PM
Then there are zero compromising and comprehensive platform tests to build towards.
So on that end I feel confident as I progress and am getting more of WPT to pass that this is the right path.
So on that end I feel confident as I progress and am getting more of WPT to pass that this is the right path.
There are decades of data out there on how browsers work that the models have been trained upon. There are very very deep and detailed specifications on how all of this is supposed to work in isolation and together.
February 15, 2026 at 6:58 PM
There are decades of data out there on how browsers work that the models have been trained upon. There are very very deep and detailed specifications on how all of this is supposed to work in isolation and together.
What I will say is that I've been actively doing this meticulously for months. This isn't a "I pumped this out over a weekend" type of AI coding session.
A browser is an interesting AI coding use case because it is incredibly complex (almost an OS) and incredibly well documented and spec'd out
A browser is an interesting AI coding use case because it is incredibly complex (almost an OS) and incredibly well documented and spec'd out
February 15, 2026 at 6:58 PM
What I will say is that I've been actively doing this meticulously for months. This isn't a "I pumped this out over a weekend" type of AI coding session.
A browser is an interesting AI coding use case because it is incredibly complex (almost an OS) and incredibly well documented and spec'd out
A browser is an interesting AI coding use case because it is incredibly complex (almost an OS) and incredibly well documented and spec'd out
Someone on reddit mocked me for "vibe coding" what I'm doing. And I get that, on the surface it seems rediculous. And there are recent examples of "we vibe coded a browser" that were shit, and one was from Cursor.
February 15, 2026 at 6:58 PM
Someone on reddit mocked me for "vibe coding" what I'm doing. And I get that, on the surface it seems rediculous. And there are recent examples of "we vibe coded a browser" that were shit, and one was from Cursor.
Sonnet 4.5 is the code exploration model being used btw.
February 12, 2026 at 4:57 PM
Sonnet 4.5 is the code exploration model being used btw.
The nice thing with Cog is that if the answer is inadequate or not found, the model will just fallback to code exploration during your work.
February 12, 2026 at 4:53 PM
The nice thing with Cog is that if the answer is inadequate or not found, the model will just fallback to code exploration during your work.
LynxJS is a UI framework. What we're building is a headless browser that can swap in render targets
February 12, 2026 at 2:26 PM
LynxJS is a UI framework. What we're building is a headless browser that can swap in render targets