Apple’s $599 iPhone-chip MacBook & Anonymous DNS via ODoH - Hacker News (May 14, 2026)

First up: Apple’s newest budget play, the MacBook Neo. The headline is simple—$599, and instead of an M‑series chip, Apple used the A18 Pro from the iPhone 16 Pro. On quick, interactive tasks, that looks clever: single-core bursts can be genuinely snappy, sometimes even flattering in benchmarks. But the more interesting part is sustained performance. In a fanless design, this machine reportedly runs full tilt for about a minute, then hits a major slowdown once heat soaks in—so big jobs like long builds, exports, or extended GPU-heavy workloads can turn into a slog. Why it matters: it’s a reminder that “fast” depends on time. Apple’s also showing how supply chain strategy can shape product design—reusing mature iPhone silicon at massive scale to hit a price point, while memory constraints and a broader DRAM squeeze reshape what “entry-level” means in 2026.

Staying with infrastructure and performance—but on the other side of the stack—Linux gaming just crossed a psychological milestone. Steam’s March 2026 numbers put Linux over 5% of users for the first time. Some of that is the Steam Deck continuing to normalize Linux as a gaming platform, and some is Windows 10 end-of-support pressure nudging people to reconsider their setups. The more technical angle in today’s discussion is NTSYNC, a Linux kernel driver that implements Windows-style synchronization primitives more natively. Why it matters: compatibility layers like Wine and Valve’s Proton have long carried the burden of making Windows games run well. Moving certain behaviors into the kernel can reduce weird edge cases—stutters, deadlocks, or the “this one game is cursed” effect. The payoff may be modest for many titles, but for the games that struggled before, stability improvements are exactly what turns a curiosity into a real platform choice.

And if you’re the kind of person who wants the future… but with the past’s interface, there’s a Windows story too. A fan-made project called Classic 7 aims to recreate the Windows 7 experience on top of Windows 10 IoT Enterprise LTSC 2021—visuals, UI behavior, even pieces of the old vibe like Aero-like styling and media-era nostalgia. Why it matters: whether you call it comfort, productivity, or muscle memory, there’s persistent demand for classic UI patterns. It also highlights an ongoing tension: people want modern security and app compatibility, but they don’t want every workflow reimagined. Projects like this fill that gap—while also reminding everyone to think carefully about trust, updates, and what you’re installing when you step outside official channels.

From operating systems to browser nostalgia: an HTML port of the classic artillery game Scorched Earth 2000 appears to be live—though what’s surfaced is a debug-heavy view rather than a polished announcement. Even in that form, it’s a neat snapshot of how preservation often happens: not as a grand release, but as something running, iterating, and slowly getting sanded down from “developer console chaos” into something people can actually play. Why it matters: the web remains one of the best distribution platforms for keeping older games accessible, especially when original binaries and platforms age out. The challenge is less about raw compute now, and more about long-term maintainability—keeping old ideas playable in new environments.

Now, let’s pivot to privacy—starting with DNS, the part of the internet that quietly reveals far more about you than most people realize. Numa v0.14 adds support for Oblivious DNS over HTTPS, or ODoH. The core idea is splitting knowledge so no single party can easily tie “who you are” to “what you looked up.” The relay sees your IP address but not your DNS query in plaintext; the target resolver sees the query but only the relay’s IP. Why it matters: ODoH has been stuck in a chicken-and-egg problem—too few relays to create meaningful diversity, and not enough users to justify more relays. Shipping a usable relay, and focusing on practical hardening like hostname validation and avoiding single-operator pairing, helps make the ecosystem less theoretical and more deployable. It won’t magically erase tracking, but it meaningfully raises the bar for passive correlation.

And while we’re talking about security: there’s a myth-busting piece making the rounds again—/dev/urandom versus /dev/random. The argument is that the popular fear—“/dev/urandom is unsafe”—is mostly outdated in practice on modern Unix-like systems. Both interfaces draw from the kernel’s cryptographically secure PRNG; the big behavioral difference is that /dev/random can block when the kernel thinks entropy is low, while /dev/urandom does not. Why it matters: blocking sounds safer, but availability is part of security. If a system hangs during startup or under load, engineers will route around it—sometimes in ways that genuinely reduce safety. The real risks are more specific: early-boot entropy issues, VM cloning, and snapshots that replicate RNG state. The fix there is better seeding and operational hygiene, not simply swapping one device file for another and hoping for “truer randomness.”

Next: a bit of Internet archaeology with real-world usefulness. A guide explains that certain U.S. “locality domains” under .us—think city and state style domains—can still be registered for free under a system that dates back to the early 1990s. The catch is that it’s not a slick modern checkout flow. It’s eligibility rules, delegated zone managers, manual review, and, importantly, you typically need to show up with working authoritative nameservers before you can even apply. Why it matters: this is a reminder that the internet isn’t one unified, modern platform—it’s layers of policy, contracts, legacy delegation, and human processes that never quite got replaced. For civic projects, local groups, or community services, a meaningful geographic domain can be valuable branding. But the bureaucracy and constraints also explain why most people never discover this path.

Two readings today broaden the lens beyond day-to-day engineering. First, an essay by John Perry Barlow—written for a conference in Japan—about his shift from rural Wyoming life into what he called “Cyberspace,” and how early online communities shaped his thinking. He frames the network as a new frontier with unclear norms, and he connects that to why digital rights groups like the EFF emerged: because the architecture of the internet can decide what privacy and free expression look like in practice. Why it matters: it’s an early articulation of a debate we’re still having—whether rights online are mainly a legal issue or a systems design issue. His core warning holds up: when borders get fuzzy, power often moves into the infrastructure.

And finally, a reported piece about the Korowai of Papua and the famous tree houses that captured Western imagination through iconic photography. The writer describes traveling to see these structures firsthand and discovering a more complicated reality: rapid change driven by settlement programs, missionaries, and cash economies—and also a feedback loop where the most dramatic tree houses are sometimes built to meet tourist and media expectations. The “image” influences the behavior, and the behavior reinforces the image. Why it matters: it’s a clean case study in how stories, incentives, and outside attention can reshape the thing being documented. In tech terms, it’s the social version of an algorithmic loop—except the stakes are culture, identity, and autonomy rather than engagement metrics.