☕️ Meta drops AI from performance reviews

• Meta scrapped AI tool usage as a performance-review metric after the criterion backfired, with executives saying internal reviews will now weigh the quality, speed, and complexity of engineers' work instead of dashboards and token counts.
• The old rule drove "tokenmaxxing," where employees burned AI tokens in bulk to climb internal leaderboards, pushing Meta's internal AI spending toward billions in 2026 and prompting plans for budgets and a central usage dashboard in 2027.
• The shift redirects evaluation away from raw token counters, meaning engineers no longer face pressure to inflate consumption just to look productive, and are instead judged on actual output rather than how heavily they lean on AI tools.

• Google has moved Chrome to a two-week stable release cycle starting with version 153, dropping the four-week schedule it adopted in 2021 across desktop, Android and iOS.
• The tighter cadence ships interoperability changes, bug fixes and security patches faster, aligning with a strategy that uses Gemini-powered automated tools to find and fix vulnerabilities, plus smaller, quicker downloads.
• Organizations avoiding the biweekly pace can stay on the Extended Stable channel, which gets weekly security fixes and major feature updates every two months; Chrome 154 arrives September 22 and is in beta now.

• Expo Modules 2.0 lets you write React Native native modules as plain annotated Swift or Kotlin classes, dropping the 1.0 DSL entirely, while making runtime calls faster than the API it replaces.
• A build-time macro reads your Swift signatures ahead of time, eliminating 1.0's reflection-style per-call allocation and dynamic type conversion, making synchronous calls 2.5 to 5.6× faster than the 1.0 API on the same SDK.
• You can try it now on iOS in SDK 57, which covers modules, functions, records, shared objects, and events via Swift macros; views and Android are still coming, with an official beta arriving in SDK 58.

• Neovim shipped vim.async, a native structured-concurrency library in its Lua standard library that orchestrates asynchronous workflows without blocking the main event loop, replacing ad-hoc callbacks and third-party coroutine wrappers like plenary.nvim and async.nvim.
• Routines run inside Tasks via vim.async.run(), scheduled cooperatively over stackful coroutines; vim.async.await() suspends a frame and yields to the loop, while child tasks attach to the parent scope and propagate unhandled errors to siblings.
• Flow-control primitives include vim.async.semaphore() for permit limits, vim.async.timeout() for cancellation deadlines, vim.async.iter() for completion-order results, and vim.async.pawait() as an async pcall; Task:wait() and Task:detach() bridge synchronous code and independent tasks.

📚 Tutorials & Advice

🔗 Other News & Articles

• Kubernetes v1.37: Advancing workload-aware scheduling LINK

• Leap second proposal will keep software stacks in sync LINK

• Super smash bros melee gets fully decompiled after over six years of effort — ambitious and technically impressive project delivers GameCube classic as C code LINK

• AI made a lot of "hideous" code but found major bottlenecks for faster Linux compilation LINK

• A “proof” of Fermat’s Last Theorem that fits the margin LINK

• Harness rebuilt its Git repository for nonstop AI agent traffic LINK

• Agents identifying as OpenAI systems wrote 17,000 posts to a wiki no one was supposed to write to LINK

📄 Papers & Resources

🧰 Latest Tools

💬 How did you find today's edition?

We read every reply — just reply to this email and let us know how we can improve!