Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Every AI agent scraping the web right now is running full chrome to do it. rendering a UI nobody looks at, for a browser that never displays a single pixel. lightpanda skips that entirely. written from scratch in zig, not a chromium fork, and it's 11x faster with 9x...

38,564 görüntüleme • 6 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

OK, I have a definitive word on the CJ Abrams play from today's Pittsburgh Pirates at Washington Nationals game after talking with Elias Sports Bureau on this. This play will stay as a sacrifice fly. The originial ruling of NOT a sacrifice fly was for the exact same reason that I thought, which is that the infielder is not running into the outfield, which is year's past would have been correct As it was explained to me, in past years, an infielder had to be running almost in a straight line towards the outfield wall to be considered "running in the outfield". Here, since he is running, and he ends up further away from home (157 feet) than when he started (145 feet), this is going to count as a sacrifice fly. That definition is changing, in part from this play to help bring greater consistency, and to take some of the guesswork out of it (the argument that he is running into the outfield as opposed to more parallel). Now, folks all the time ask "why doesn't MLB publish the OS Manual" and I always say because it is a living document that can have the wording change, and the wording for this play will be modified to something like "more towards the outfield wall than towards home plate" to eliminate any confusion. The big key to this play is that he was running on a full sprint. Also, and this is helpful for me, but for all fly ball outs that score a run, Elias Saba reviews to ensure consistency. So, yes, it's a sacrifice fly, and now that I have that info from Elias themselves, that sort of settles this one. Sounds like the guidelines for this definition will be changing, either this season, or certainly for next season.

MLB Scoring Changes

49,079 görüntüleme • 25 gün önce

hey if you have a 3060, or any GPU with 8GB or more sitting in a drawer right now, that thing can run 9 billion parameters of intelligence autonomously. and you don't know it yet. 2 hours ago i posted that 9B hit a ceiling. 2,699 lines across 11 files. blank screen. said the limit for autonomous multifile coding on 9 billion parameters is real. then i audited every file. found 11 bugs. exact file, exact line, exact fix. duplicate variable declarations killing the script loader. a canvas reference never connected to the DOM. enemies with no movement logic. particle systems called on the class instead of the instance. fed that list as a single prompt to the same Qwen 3.5 9B on the same RTX 3060 through Hermes Agent. it fixed all 11. surgically. patch level edits across 4 files. no rewrites. no hallucinated changes. game boots. enemies spawn, move, collide. background renders. particles fire. and here's what nobody is talking about. this is a 9 billion parameter model running a full agentic framework. Hermes Agent with 31 tools. file operations, terminal, browser, code execution. not a single tool call failed. the agent chain never broke. most people think you need 70B+ for reliable tool use. this is 9B on 12 gigs doing it clean. the model didn't fail. my prompting strategy did. the ceiling is not the parameter count. the ceiling is how you prompt it. this is not done. bullets don't fire yet. boss fights need wiring. but the screen that was black 2 hours ago now has a full game rendering in real time. iterating right now. anyone with a GPU from the last 5 years should be paying attention to what is happening right now.

Sudo su

683,576 görüntüleme • 4 ay önce