this is fucking hugeeeeeee for jj adoption LFG

📦 NVIDIA did it first, now we are releasing 2,600+ free game-ready 3D models (+200 each week). For good. 🎛️ Each model is a program, with parameters you can tweak to customize look, state, season, color, wear, etc. All thanks to the $500,000 in funding we received from @xprize and @GeminiApp and all of our early individual funders, thank you all! Go build. polyfork.dev

We put Jev inside the Lightpanda binary and built judge() on top of it. @typesafeai No more sending a whole page to an LLM just to find out it's a cookie banner. > Blocked pages, CAPTCHAs, cookie walls, logins, paywalls, error pages, empty searches and pages still loading can all return an HTTP 200 > judge() asks a set of predefined questions and tells you if the page has real content, and what kind: article, listing, product or docs > One call, ~0.2s In the video: > 30 sites, ~14s total > Lightpanda backs off when rate-limited, accepts cookie walls, and keeps or skips each page

made a tool for searching for PCB assy/fabs throughout the world: zackslab.com/atlas if you're favorite pcb house isn't on here lmk :)

We’re bringing Aristotle to code. AI is writing more code than anyone can review. We're building the AI that verifies it. Starting today with C and Verilog.

The Rust team read thousands of survey answers about variadic generics by hand, and chose not to use AI to do it. 🦀 The Variadic Generics Micro Survey results are out on the Inside Rust blog, by Olivier Faure. The survey ran a year ago, with over 3,300 submissions. The team considered using AI to process the free-text answers. They decided against it over privacy and quality concerns, and went through the data by hand. The post says that is why the results took so long. What the answers show: → The most common use: implementing a trait for tuples of every size. Today that is done with macros up to a fixed size → Others named parser combinators, SQL queries with a variable number of columns, tensor types that catch dimension mismatches, and struct-of-arrays layouts → Some hit the maximum tuple size they had provided for, and users then needed more → Some gave up on an approach entirely. One example: falling back to boxed trait objects, not because boxing was wanted, but because tuples of differently typed values do not work generically On the macro workaround, most were neutral. About 7 said macros are enough. More people strongly disliked them. The skeptics matter too. Their most frequent worry is that Rust could suffer death by a thousand cuts, with many small arcane features making it hard for new users. They were a minority, but large enough that future proposals should not ignore them. The overall mood, in the post's words: cautious, but interested. The takeaway for any future proposal: a syntax that reads easily, and clear upsides over the macro workarounds. Worth keeping in mind: → The survey was self-selected, and the post notes that the Bevy community is over-represented → The post admits the example for one question was too leading → This is a survey of wants. It does not commit Rust to anything 🔗 blog.rust-lang.org/inside-ru… #RustLang #ProgrammingLanguages #LanguageDesign #OpenSource

Lisp has already been top 3 lang, decades ago, why should we try to regain old achievements when we can have new ones? 😎

Wax, a Rust-like syntax for WebAssembly. Rust-like syntax gives me eye cancer, but nevertheless an interesting project: github.com/ocsigen/wax h/t @warianoguerra

‼️ ALERT - 2 New critical Wasmtime flaws (CVSS 9.9) could let malicious WebAssembly modules escape their sandbox. • CVE-2026-115889 Affects multiple architectures • CVE-2026-115893 ARM64-only, present since 2020 Embedded apps need rebuilding. Read ↓ thehackernews.com/2026/10/tw…

Minimal Phone 2 starts from $600 Used BlackBerry Q10: $60 Reverse engineered it and got a physical keyboard, SSH, and Claude Code in my pocket