8GB Mac beats cloud queries & Dolphin expands into Triforce arcade - Hacker News (Mar 12, 2026)

An 8GB laptop with an iPhone-class chip just beat some cloud machines at analytical database queries—at least in the scenario people forget to benchmark. How did that happen, and what does it say about modern performance? Welcome to The Automated Daily, hacker news edition. The podcast created by generative AI. I’m TrendTeller, and today is March-12th-2026. Let’s get into what matters, and why.

8GB Mac beats cloud queries

Let’s start with that benchmark surprise. DuckDB put Apple’s newly released entry-level MacBook Neo—just 8GB of RAM, running an A18 Pro—through ClickBench and TPC-DS to see if it can do “real” analytics work. In a cold-cache run of ClickBench, the Neo actually came out on top, finishing the whole query set in under a minute. The twist wasn’t magical CPU power; it was storage. Local SSD access avoided the network-attached latency that can quietly kneecap cloud instances when nothing is warmed up yet. In hot-cache runs, a huge cloud box still dominated, as you’d expect. But the Neo held its own against a mid-sized cloud machine on typical query times, despite having far fewer cores and far less memory. On TPC-DS, DuckDB’s out-of-core behavior pushed beyond the 8GB limit by spilling to disk—proof the system can keep working when memory runs out—but it wasn’t pretty for sustained workloads. The takeaway is practical: for occasional local crunching or as a fast client for cloud workflows, it’s plausible. For daily big analytics, the constraints show up fast—and caching and storage paths can matter as much as raw CPU.

Dolphin expands into Triforce arcade

Staying in performance-land, Dolphin Emulator’s Release 2603 is a big one—especially because it’s not just about GameCube and Wii anymore. Dolphin now has its first official support for the Triforce arcade platform, which is a notable expansion in scope and preservation value. On the speed and playability side, Dolphin overhauled key parts of its “fast memory” approach so more games that use unusual memory tricks run dramatically better. The headline beneficiary is Rogue Squadron III, which can now reach full speed on high-end PCs where it previously struggled. There’s also work aimed at reducing major stutters—things you feel immediately as a player, like camera transitions. And one of the most satisfying fixes in this release: a years-long online desync problem in Mario Strikers Charged was traced to subtle floating-point rounding behavior. Correcting that makes matches stable even between Dolphin and real Wii hardware. It’s a reminder that emulation progress isn’t only about frames per second—it’s also about tiny correctness details that decide whether multiplayer and timing-heavy games actually work.

Temporal replaces JavaScript Date finally

On the JavaScript front, Temporal has reached Stage 4 at TC39, which means it’s officially on track to land as a standardized part of ES2026. This is the long-awaited attempt to move the web away from the famously awkward Date API—an artifact of 1995 design decisions that never aged well. Why it matters: time zones, daylight saving time shifts, and calendar math are where production systems go to die—quietly and repeatedly. Over the years, the ecosystem patched that gap with popular libraries, but at the cost of bigger bundles and duplicated time zone data across apps. Temporal’s promise is simpler and safer defaults: immutable types, explicit time zone handling, and fewer footguns around parsing and arithmetic. It’s also a win for consistency: when the platform provides a solid time API, everyone spends less time reinventing one.

3D engine math without trig

If you build 3D software, there’s a sharp little argument from graphics programmer Inigo Quilez: stop reaching for trig functions as the first tool for orientation math. The point isn’t “sin and cos are bad,” it’s that many engine internals already have the geometry they need, and converting vectors into angles—and then immediately converting angles back into vectors—adds cost and fragility. The interesting part here is the mindset shift. Dot products and cross products already encode the relationship between directions in a way computers like: direct, stable, and usually cheaper. So instead of sprinkling acos and atan around your codebase, you can often keep the math in vector form and get something that’s both faster and less likely to blow up at edge cases. This kind of cleanup rarely makes headlines, but it’s exactly how real-time systems get more robust over time.

Static-site decentralized social protocol

Now for a very different flavor of “systems thinking”: a proposed decentralized social protocol called s@, or the sAT Protocol. The design runs entirely on static websites, with each person hosting their own posts and social data on their own domain. No central server, no relay network, and importantly, no global firehose that encourages performative broadcasting. The bet is on smaller, mutual-follow networks—closer to the early web and RSS culture—combined with modern crypto. Posts are encrypted, followers get access via per-person key wrapping, and mutual-follow is treated as a built-in spam filter. The trade-off is clear: you give up easy virality and mass discovery, but you gain autonomy, portability, and a social graph that isn’t trapped behind a platform’s business model. Even if this exact protocol doesn’t take off, it’s an instructive experiment in what “social” looks like when it’s built like personal infrastructure.

Private credit defaults hit record

Zooming out to markets and risk: Fitch says defaults among U.S. corporate borrowers using private credit hit a record 9.2% in 2025. That’s up from the previous record the year before, and it’s happening across sectors, with many defaults concentrated among smaller companies. The key driver Fitch points to is pretty straightforward: lots of floating-rate loans, not much hedging, and policy rates staying high longer than many borrowers could tolerate. Private credit has grown into a major pillar of corporate financing—especially for middle-market firms—so higher default rates don’t just hurt a few lenders. They can change risk appetite, refinancing availability, and the terms companies face even if they’re healthy today.

SBCL’s reproducible Lisp bootstrapping

In programming language land, there’s a paper digging into how Steel Bank Common Lisp—SBCL—bootstraps itself, and why that build strategy matters socially as much as technically. Many Lisp systems historically rebuild by mutating an existing image, which can be powerful but also opaque and hard to reproduce. SBCL’s approach aims for a cleaner slate: use a cross-compiler hosted in another Common Lisp, compile into SBCL’s object format, and then assemble a fresh memory image in a dedicated step. The practical upside is reproducibility and a lower barrier for contributors—fewer rituals, fewer “you have to know the magic boot sequence” moments. The broader lesson generalizes well beyond Lisp: build pipelines shape who can participate, and how confidently a project can evolve.

Tic-tac-toe powered by printf

And because Hacker News never misses a good mind-bender: security researcher Nicholas Carlini posted an obfuscated C program that plays tic-tac-toe with effectively one gigantic printf. The stunt relies on format-string features—especially the parts that can write values back into memory based on how many characters were printed. This is half puzzle, half cautionary tale. It’s a clever demonstration that “output formatting” can be turned into computation if the language lets you cause side effects in the formatting layer. It’s also a neat reminder of why dangerous format-string features are treated with suspicion in security work: tools meant for convenience can become surprisingly expressive—and surprisingly abusable—when pushed to extremes.

Ruby on Rails feels simpler

Finally, a more grounded developer story: someone returned to Ruby on Rails in 2026 and found that Rails 8 has quietly leaned into simpler defaults for small apps—more interactivity with less custom JavaScript, and fewer external moving parts for common infrastructure. The interesting angle isn’t hype; it’s trade-offs. Rails is arguably less fashionable than it once was, and parts of the ecosystem feel slower-moving. But Rails continues to optimize for getting a traditional web app shipped with minimal operational overhead—especially when paired with modern deployment tooling. In a world where complexity keeps creeping up, there’s real value in frameworks that keep saying, “you probably don’t need all that.”

Bonus quick detour into manufacturing tech: a guide on so-called “3D knitting,” or Wholegarment knitting, explains how computerized machines can produce a sweater as a single seamless piece directly from a digital design. The relevance here is the same theme we saw in software: fewer joins, fewer failure points. Eliminating seams can improve durability and comfort, and the process can reduce waste compared to cutting shapes out of fabric. It’s also part of a larger shift toward on-demand production—making items when they’re ordered, not guessing inventory months ahead. If that scales, it changes where and how apparel gets made, and pushes clothing a bit closer to the software model: automated, localized, and configurable.

That’s it for today’s Hacker News roundup. If you want to dig deeper, links to all stories can be found in the episode notes. I’m TrendTeller—see you next time on The Automated Daily, Hacker News edition.

8GB Mac beats cloud queries & Dolphin expands into Triforce arcade - Hacker News (Mar 12, 2026)

Our Sponsors

Today's Hacker News Topics