LodeHQ
AI news for people who shipFree, by email

Dev · Sunday, 2 August 2026 · Issue 64 · 12 stories

Go 1.27 generics, Chrome CSS if(), stacked PRs

Languages & Frameworks

Chrome 137 introduces CSS if() for inline conditional styles

Chrome 137 ships a new CSS if() function that lets you embed conditional logic, media, style, or supports queries, directly in property values. This replaces separate @media blocks and enables cleaner, inline styling for responsive layouts, feature detection, and UI state. Developers can now write tighter CSS without juggling multiple rule sets.

developer.chrome.com ↗3 min read at source

Tools & Platforms

AI-Assisted Development

Open-Weight LLMs Match Proprietary Accuracy on New ClinReg Benchmark

The ClinReg benchmark for life‑science regulatory filings shows that open‑weight models like Llama 3, Mistral Large, and DeepSeek now hit the same accuracy scores as closed‑source giants on knowledge and reasoning tests. This closes a key gap for cost‑effective AI in pharma, letting companies replace pricey proprietary APIs without sacrificing compliance‑critical performance.

Stateless MCP 2.0 streamlines AI tool integration, spawns Explorer and Datasette plugins

MCP 2.0 drops the two‑step session model for a single‑request, stateless flow, cutting client and server complexity. Simon Willison demoed the change by releasing mcp‑explorer, datasette‑mcp and an early llm‑mcp‑client, making it easier for developers to audit and scale LLM‑powered tool calls. The leaner spec could revive AI agent adoption on modest hardware.

simonwillison.net ↗6 min read at source

Engineering Practice

Eval Gates Add CI Safety to Prompt Changes

Prompt tweaks can silently degrade LLM outputs. By treating each change like a code commit and inserting an evaluation gate in Azure, teams can automatically test prompts against a fixed suite before promotion, catching regressions early. This adds a CI‑style safety net without building custom infrastructure.

luke.geek.nz ↗4 min read at source

Stop Using CustomEvent: Subclass Event Instead

CustomEvent was a stopgap for browsers that couldn’t subclass Event; modern browsers support native class inheritance, so using CustomEvent forces developers to juggle the awkward `detail` payload. Subclassing Event gives type‑safe, intuitive events that behave like native MouseEvent, reducing boilerplate and leaking fewer implementation details. Switching now modernizes your component APIs.

justinfagnani.com ↗6 min read at source

Careers & Open Source

You’re caught up.

That was all 12 stories in the 2 August issue.