Saturday, 20 June 2026

Norway near-bans AI in elementary schools to protect developing minds; Project Valhalla ships in JDK 28 after a decade; Lorin Hochstein on why LLM-written incident reports hollow out retrospectives

Engineering

JVM Weekly

Project Valhalla, Explained: How a Decade of Work Arrives in JDK 28

After a decade of development, Project Valhalla ships its core feature in JDK 28: the `value` modifier, which creates objects without identity and allows the JIT to eliminate heap indirection by scalarizing them and flattening them directly into arrays and fields. The target is the performance gap that has long forced Java developers doing data-intensive work — game engines, HPC code, financial modeling — to hand-code primitive arrays or accept the overhead of object pointers. Backward compatibility is preserved: existing code and null handling continue to work, while value-typed classes gain the memory characteristics previously reserved for primitives. For a language whose identity semantics were baked in from 1995, the change is foundational — the result of Valhalla's guiding insight that 'codes like a class, works like an int' required making identity something you explicitly request rather than the default you always get.

Read →

Overreacted (Dan Abramov)

There Are No Instances in ATProto

Dan Abramov argues that AT Protocol's most important architectural property is routinely misunderstood: atproto has no 'instances' the way Mastodon does because it treats data hosting and application aggregation as independent concerns. In Mastodon, one server handles both your data and your social graph view — which means the instance operator controls your discoverability and migrating away is disruptive. Atproto decouples them: a Personal Data Server holds your posts, while any app aggregates across all PDSes independently. The analogy is RSS — a feed is hosted anywhere and any reader can consume any feed; no one node controls what you can discover or reach. The implication is that 'decentralization' means very different things depending on what is and isn't separated, and atproto concentrates the work of decentralization at the protocol layer rather than leaving it to instance politics.

Read →

Tales from Production

Google Workspace Threatening to Block Firefox

Google Workspace has been displaying persistent warnings to Firefox users urging them to 'secure their device' by switching to Chrome — despite Google officially designating Firefox, Safari, and Edge as fully supported browsers. When pressed, Google support described the warnings as targeting admins only and framed them as recommendations rather than requirements, a characterization at odds with the alarming phrasing of the warning itself. The episode is a case study in how large platform vendors can leverage control over essential productivity tools to steer users toward their own browser without triggering formal interoperability obligations: the warnings are technically optional but behaviorally coercive when they appear inside tools organizations depend on daily. For administrators responsible for multi-browser environments and compliance testing, the practical effect is pressure to narrow the browser landscape regardless of the formal support policy.

Read →

Kent Beck (newsletter)

Hey, n00b, We Didn't Hire You to Complete Tasks

Kent Beck argues that what organizations say they want from junior engineers — task completions — and what they actually need — learning capacity — are different things, and that conflating them produces a metric that AI now makes almost meaningless. The distinction between B-level and A-level performance lies not in completion velocity but in learning velocity: A-level engineers challenge assumptions about what problem is worth solving, discover high-leverage solutions others miss, refactor to reduce future costs, and document insights so the team benefits. The piece is implicitly a response to the era where junior 'complete-tickets-quickly' work is most directly exposed to automation: if a new hire's value is throughput alone, that value is substitutable. The durable case for hiring and developing junior engineers rests on how quickly they grow — which requires creating conditions where growth is possible rather than optimizing purely for output.

Read →
Humanities

JSTOR Daily

The Nuclear Test Site That Advanced Oceanography

After the 1946 nuclear tests at Bikini Atoll, the Navy returned in 1947 with a large scientific team that drilled 2,556 feet into the reef — and in the process confirmed Charles Darwin's theory of atoll formation and helped launch modern oceanography as an interdisciplinary discipline. The expedition recovered corals, algae, foraminifera, and mollusks at nearly every depth, providing physical evidence for Darwin's subsidence hypothesis that surface fieldwork could never have reached. Historian Ronald Rainger argues the story complicates both the 'military coopts science' and 'scientists exploit military funding' narratives: researchers knowingly and willingly did military work because they genuinely needed the Navy's ships, drills, and institutional access, while the Navy needed their expertise for navigation and submarine warfare — a symbiotic arrangement in which scientists progressively gained control over research design. The episode is an early instance of a recurring pattern in twentieth-century science: transformative capability requiring resources that only defense budgets commanded, with the knowledge produced outlasting and outrunning its military origins.

Read →

Crooked Timber

In Honor of National Indigenous Peoples Day (Canada)

Two vignettes from early Canadian colonial history illuminate how systematic failures of epistemic humility and deliberate information asymmetry shaped outcomes across centuries. The 'Bad Overwinter' pattern — where European colonists repeatedly died in preventable numbers because they dismissed Indigenous knowledge while misreading familiar latitude markers as a proxy for familiar climate — shows how confidence in abstract metrics combined with social prejudice proved lethal, repeatedly; Samuel Champlain listened to local expertise and survived, but his deference was read as a political liability rather than sound epistemics because he lacked the aristocratic standing to make knowledge from Indigenous sources count. The countervailing story is sophisticated information warfare: a single Innu trading group ran a 40-year monopoly on the Saguenay fur trade by manufacturing opposing terror narratives simultaneously for French traders and interior nations — an early case of sustainable market power built entirely through manufactured information asymmetry. Read together, the two stories make a pointed argument about what 'not knowing what you don't know' has historically cost, and what mastery of the information environment has historically enabled.

Read →