Related reading
Faster Starts, Less JavaScript Overhead
Codename One reduced startup latency and JavaScript overhead by publishing screen state atomically, indexing style lookups, avoiding unnecessary artwork generation, and refining suspension analysis, yielding measurable speedups.
CodeName Onecodenameone.com7 min20+ years of running "alpha quality" browser as my main web browser
The author has been using Firefox Nightly for about 20 years, mixing personal and work usage while regularly filing crash reports. He argues that nightly builds can be stable enough for daily work and that crowd‑testing and crash telemetry are valuable for Mozilla’s stability team.
Mozilla Automation Teamhirlimann.net3 minFrom PrismJS to Better PrismJS to MicroLighter in Three Painless* Steps
The author describes evolving syntax highlighting on their Eleventy site, starting from the default PrismJS plugin to a custom server-side hack for line numbers. They then detail integrating MicroLighter, a client-side web component, by leveraging Eleventy's bundler for conditional loading and managing content escaping for optimal performance.
Alex Russellinfrequently.org6 minSmall Programming Tricks
A grab‑bag of command‑line, SQL, and JavaScript shortcuts – from fuzzy‑searching shell history with fzf to using `SELECT` without a `FROM` in Postgres, `git log -S`, and keeping an HTTPS agent alive in Node. The author argues that such bite‑size tips boost daily productivity and suggests sharing one per day on a team channel.
Fixing Server Component Bundle Leaks in Next.js with AST Linting
Server‑only code can silently inflate client bundles in Next.js 15+ apps. The article shows how to spot leaks with @next/bundle-analyzer, prevent them by removing shared barrel files or adding the `server-only` guard, and enforce a deny‑list of server modules via a custom ESLint rule that scans the AST of files with a `'use client'` directive. The rule is wired into a CI bundle‑budget check using…
SitePointsitepoint.com14 min
