fastrender

ll Claude to whoever is thinking of planning the next mass layoff. Their definition of "AGI" is different to yours. The correct answer to all of this pricing nonsense that Anthropic and others are doing is local open weight models that you run on your own machine. They know this and powerful local models undercut their entire business model if hosted by others or if a smaller local model matches the performance of larger ones. [1] https://github.com/anthropics/claudes-c-compiler [0] https://github.com/wilsonzlin/fastrender

ue stress testing the boundaries of coding agents and report back on what we learn. > Code here: https://github.com/wilsonzlin/fastrender

I would save you a ton of typing and you'd be able to iterate on your idea. There are plenty of layout/graphics/Js components out there to choose from, so you could ensure a relatively small and clean POC. Someone doing that, with or without AI but with a good idea, would impress me. FastRender on the other hand is just this humongous pile of spaghetti, and my guess is it still is entirely dependent on existing libraries for actually showing something to the screen. So that's the clear fail of the agent in my opinion: why produce so much code when it could be done so easily otherwise. Also, why bs yourself into these architecture docs and pretend you are following the specs when in fact you are not? Everytime I try to browse the code I give up, mostly because when I look at something to try to understand how it fits into the whole, I end-up realizing it's only used in some unit-test. For a quick comparison: - https://github.com/DioxusLabs/blitz/blob/f828015b26d32b0bed3... - https://github.com/wilsonzlin/fastrender/blob/19bf1036105d4e... I believe the two are more or less doing the same, but one is 30x the size of the other. I can't begin to understand the render loop of Fastrender from the code. On the other hand, here is the one from Blitz shell(the default Blitz app putting together various modular components): - Window runs in winit loop: https://github.com/DioxusLabs/blitz/blob/f828015b26d32b0bed3... - Redraw is at https://github.com/DioxusLabs/blitz/blob/f828015b26d32b0bed3... - Calls into `paint_scene`, using the generic scene from the generic renderer: https://github.com/DioxusLabs/blitz/blob/f828015b26d32b0bed3... Simple as that, and with a nice idea in terms of modularity. That's a POC web engine.

around the code because I know the web specs. So I agree this isn't just wiring up of dependencies, and neither is it copied from existing implementations: it's a uniquely bad design that could never support anything resembling a real-world web engine. Now don't get me wrong, I do think AI could be leveraged to build a web engine, but not by unleashing autonomous agents. You need humans in the loop at all levels of abstractions; the agents should only be used to bang out features re-using patterns established or vetted by human experts. If you want to do this the right way, get in touch: https://github.com/gterzian

ntributor committing whatever they want. And a "judge agent" is not the same thing as a human code owner as reviewer. Example on how not to do it: https://github.com/wilsonzlin/fastrender/blob/19bf1036105d4e... This rendering loop architecture makes zero sense, and it does not implement web standards. > in the HTML Standard, requestAnimationFrame is part of the frame rendering steps (“update the rendering”), which occur after running a task and performing a microtask checkpoint > requestAnimationFrame callbacks run on the frame schedule, not as normal tasks. This is BS: "update the rendering" is specified as just another task, which means it needs to be followed by a microtask checkpoint. See https://html.spec.whatwg.org/multipage/#event-loop-processin... Following the spec doesn't mean you cannot optimize rendering tasks in some way vs other tasks in your implementation, but the above is not that, it's classic AI bs. Understanding Web standards and translating them into an implementation requires human judgement. Don't use an agent to draft your architecture; an expert in web standards with a interest in agentic coding is what is required. Message to Cursor CEO: next time, instead of lighting up those millions on fire, reach out to me first: https://github.com/gterzian