Plutonic Rainbows

Alexander McQueen's Autumn/Winter 1995 show still has the unpleasant force of something fashion could not quite metabolise. It was presented in March 1995, with heather and bracken on the runway and women walking in slashed lace, torn tartan, exposed bodices, and the low-slung bumster line that made the body look newly vulnerable. The clothes did not ask to be admired first. They made admiration feel like part of the problem.

The misunderstanding arrived almost immediately. The title was read as an image of violence against women, helped along by the staging: battered-looking models, cut-open garments, a performance language that blurred fashion show and assault scene. The Met's account of McQueen and tartan is useful because it states the harder claim plainly. McQueen meant the word as the historical rape of the Scottish Highlands by English landlords, not as a fantasy of sexual violence. That does not make the show comfortable. It makes the discomfort more exact.

McQueen was not using tartan as a heritage print. The Met identifies the black, red, and yellow McQueen sett in the collection, while PatternVault notes that the show used Lochcarron tartan and lace found in Brick Lane. Those details matter because the work sits between clan history, market material, and London rag-trade improvisation. It is not a pure return to origin. It is origin cut up, bought by the yard, stitched into a jacket that refuses to close politely.

I like tartan least when fashion makes it cosy. A scarf, a school uniform, a Christmas tin, a version of Scotland packaged for people who want landscape without politics. McQueen would have hated that softness, or at least distrusted it. PBS quotes him, via Andrew Wilson's biography, rejecting what he called Vivienne Westwood's "fake history" of romantic tartan, and saying eighteenth- century Scotland was not beautiful women drifting over moors in chiffon. It is a sharp line because it also risks sounding ungenerous. Westwood had her own politics, her own rage. However, McQueen's point lands: romance can launder damage until the costume looks innocent.

The show was not tasteful, and I don't think it was trying to be. Taste would have made tartan decorative again. McQueen wanted it to accuse the room, to pull a textile out of tourist romance and put the violence back into the pattern. The nineteenth-century bodice references, the breast-exposing cuts, the broken lace, the heather underfoot: all of it pushed against the idea that history becomes harmless once it has become beautiful.

There is a line from this to the other mid-nineties runway arguments that kept attacking fashion's own manners. Margiela's playground show removed the front row and made the hierarchy look like furniture. Gaultier's Les Tatouages pulled body modification into luxury before it had become celebrity grammar. McQueen's move was harsher because it did not only rearrange taste. It made taste feel morally exposed.

Tim Blanks later called the show legendary and remembered it as an image-building exercise from a designer not yet making clothes in the ordinary commercial sense. That sounds almost too strategic, as if the shock were only branding. However, the surviving garments argue against reducing it to publicity. The McQueen house's own Barbican exhibition page identifies Look 06 as a fragile lace dress, hand-cut and dyed, with a latex-coated bodice and fishing-wire binding. A piece like that is not merely an outrage delivery system. It is craft under stress.

Maybe that is why the show keeps refusing to settle into a single verdict. It was exploitative and serious, theatrical and historically literate, a young designer's bid for attention and a real argument about what fashion does to national memory. The later archive has learned how to hold it, glass vitrine, museum caption, published essay, careful phrasing. I am glad those captions exist. I also hope they never make the show sound resolved.

A drained swimming pool looks less abandoned than interrupted. The blue tiles still imply depth. The lane markings still point forward. Even the echo seems to be waiting for a class of children to arrive in shoes they are not allowed to wear near the water. A closed municipal baths is not quite a ruin, at least not at first. It is a public promise with the plug pulled out.

Britain's public baths were never only about leisure. The official story runs through sanitation before it reaches swimming: the Baths and Washhouses Act of 1846 encouraged local authorities to build places where people could wash themselves and their clothes. A White Rose thesis on aquatic leisure in England dates Liverpool's St George's Baths to 1828 and calls it the first indoor municipal swimming pool in England, but the later legislation gave the idea a municipal grammar. The point was comfort and health. It was also class, because many of the homes most in need of those baths did not have bathrooms of their own.

That is why these buildings carry a charge beyond nostalgia. Worlledge Associates' short history of swimming pools notes that from the 1850s hundreds of municipal pools and bath houses were built across the country, often in working-class city areas. Some were modest. Some were grand enough to make local government look almost priestly, brick and stone insisting that hygiene was part of citizenship. I don't want to over-romanticise that. Public bathing also meant discipline, queues, separate facilities, supervision, rules about what kinds of bodies belonged where. Still, there was something startling in the premise: the town owed you water.

The later pools changed the emphasis without losing the civic idea. A Guardian piece on Britain's swimming-pool culture describes Aberdeen's Bon Accord Baths as dating from 1937, with a four-tier diving platform and what it calls Scotland's deepest deep end. The same piece notes that nearly 200 public baths were built between 1960 and 1970, and that Dollan Baths in East Kilbride took its humpback profile from Kenzo Tange's 1964 Tokyo Olympics gymnasium. That detail is almost too good: a Scottish new-town pool borrowing a shape from Japanese modernism, then translating it into the Saturday smell of chlorine, coin lockers, and wet hair in winter air.

A closed municipal pool feels wrong because it was built to make private life public for an hour. Bodies, lockers, verrucas, damp towels, the smell of disinfectant, a whistle from somewhere above the water: civic intimacy was tiled, supervised, and timed. ArchDaily's account of public pools as urban spaces is useful here because it treats bathing as a social arrangement, not just a facility. Pools strip away ordinary status markers, though never perfectly, and they have also carried the uglier politics of segregation, surveillance, and exclusion. The egalitarian fantasy was always leaky.

The closures hurt because they don't remove a luxury. They remove one of the few municipal rooms where people were allowed to be awkward together. Local authority cuts and ageing buildings have made the old pools expensive to keep. Bon Accord closed in 2008. Elsewhere, campaigners try to save lidos, restore baths, or reheat the dream in new ways. Something Curated's account of the V&A and RIBA exhibition on pools points to Penzance's Jubilee Pool, refurbished by Scott Whitby Studio with geothermal heating; the pool's own site now calls it the UK's largest seawater pool and gives its geothermal water at 28 to 30 degrees.

That revival is heartening, but it also sharpens the loss. The surviving pool becomes special, photogenic, fundable, a heritage object with a good story. The ordinary municipal baths was not meant to be special. It was meant to be there. Every town had its version, or should have done: a building where public health, exercise, boredom, embarrassment, and cheap heat met under a high roof. When the water goes, what remains is not silence. It is the sound of a local authority retreating from the body.

Monterey Park has done something the AI buildout was not supposed to make easy. It turned a data center into a local ballot question, then answered it with a landslide. The official Los Angeles County results page showed Measure NDC ahead by 6,602 votes to 1,041 as of Wednesday afternoon, a margin of 86.38 percent to 13.62 percent. That is not a hesitant protest vote. That is a city saying it has heard enough.

The measure matters because of its form as much as its substance. Monterey Park had already moved against data centers by ordinance, after a proposed 247,000-square-foot facility drew local anger. The Los Angeles Times reported that the site would have been less than 500 feet from the nearest home and would have used three times the electricity of the 60,000-person city. Measure NDC makes the ban harder to unwind. The county result text says the prohibition continues until ended by voters, which means a future council cannot quietly trade the policy away after developers change their pitch deck.

That is the part Silicon Valley should find unnerving. Not because every town will copy Monterey Park exactly. Most won't. Data centers arrive with tax promises, construction jobs, utility upgrades, and the dull authority of national strategy. However, the local objection now has a working shape. Put it on the ballot. Name the thing plainly. Ask whether a neighborhood wants to host the physical cost of someone else's model race.

The AI industry likes to talk about infrastructure as if it were an abstraction: compute, capacity, clusters, gigawatts. Monterey Park answered in the older language of city politics. A building goes somewhere. The noise goes somewhere. The diesel backup generator is not a metaphor. The ratepayer sees the bill, or fears seeing it, and the fear does not become less political because the server racks are meant to support an impressive benchmark.

Politico described the vote as part of a wider backlash against AI infrastructure, with concerns about electricity, water, and air pollution from backup generators. Government Technology, republishing the Los Angeles Times story, noted temporary moratoriums in Montebello, El Monte, and Baldwin Park, plus an Alhambra zoning-code ban. Newsweek's map pushed the frame wider again, pointing to moratoriums and possible bans in places as different as Denver, Tulsa, Huron County, and several New Jersey municipalities. The pattern is not yet a wall, but it is more than a NIMBY reflex. It is a new veto point.

I wrote about [Maine's data-center moratorium][maine] in April, and that story felt like the state version of a coming argument: how much grid, land, water, and patience should be reserved for machines whose owners live somewhere else. Monterey Park makes the argument smaller and therefore sharper. A city about ten miles east of downtown Los Angeles did not need to settle the future of AI infrastructure. It only needed to decide whether one category of building belonged inside its limits.

There is a temptation to treat this as symbolic, because one city cannot slow the global hunger for compute. Maybe not. But symbols become procedures when they work. Measure NDC gives opponents a script, and the script is simple enough to travel: no emergency theory of AI, no technical essay about model scaling, just a municipal question about noise, power, water, air, and who gets to decide. [maine]: /posts/2026-04-19-maine-gets-there-first.html

The small brick electricity substation behind the shops was one of the first places where ordinary suburbia admitted it had a dangerous interior. Not a factory, not a railway line, not a derelict house with boards over the windows. Just a low municipal block with a metal door, a fence, weeds in the gravel, and a yellow sign that did not bother with euphemism. Danger of death. The phrase had the bluntness of a spell.

I remember these buildings as local shrines to adult knowledge. They sat at the edge of shopping parades, council estates, playing fields, and service roads, near enough to be part of childhood geography but never available for use. You could press your face to the mesh and see almost nothing: ceramic insulators, grey cabinets, a warning plate, perhaps the hum if the afternoon was quiet. The point was not secrecy. The point was that the real work of the place happened without any human scale attached to it.

That is why the old electricity safety films landed so hard. The BFI record for Play Safe - Frisbee dates it to 1978 and gives the plot in almost perfect miniature: a girl urges a boy to enter a sub-station to retrieve a Frisbee. Another BFI record for Play Safe - Kites and Planes names David Eady as director, the Electricity Council as sponsor, and Brian Wilde in the cast. These were not gentle lessons. They were tiny moral panics with voltages attached. They belong to the same teatime culture of calibrated fear.

The fright worked because the setting was already familiar. Every child knew a substation, or thought they did. It was where the ball went. It was where the older boys pretended they had climbed in. It was where the council grass stopped being grass and became infrastructure. Public information films did not invent the terror; they gave it editing, music, and a corpse.

The adult version is less theatrical and more revealing. National Grid explains that substations change voltage so electricity can move across the network and then become usable again. Electricity may leave a power station at around 10 to 30 kV, get stepped up as high as 400,000 volts for transmission, then stepped down through the system for ordinary appliances. EMFs.info describes local distribution substations as the common near-home sort, transforming higher voltage electricity to normal mains voltage, with many hundreds of thousands of similar sites across the UK, each typically serving up to a few hundred houses.

That should make them banal. Instead it makes them stranger. The substation is the exact point where an abstraction becomes domestic: national power, bills, kettles, immersion heaters, bedroom lamps, the television warming up after school. A whole house enters through a forbidden brick kiosk nobody visits unless something has gone wrong.

Historic England's utilities guide is useful here because it refuses to treat such structures as invisible by default. Its electricity section notes that local sub-stations, distribution kiosks, and pylons can carry design or landscape significance; it also points to Moore Street Electricity Substation in Sheffield, listed Grade II for architectural interest. That is the part I like. The ugly little building is not automatically outside culture. Sometimes it is culture with a padlock on it.

Online maps have made service spaces more legible, though not less odd. You can now search, label, photograph, and complain. The old uncertainty has thinned out. A place that once existed as a warning sign and a neighbourhood rumour can become a pin, a planning document, a street-view angle. Yet the mood survives, because legibility is not intimacy. Knowing what a substation does does not make it welcoming.

The substation was not hidden. It was worse than hidden: visible, labelled, fenced, and unexplained. Children knew it mattered because adults had made it ugly on purpose, then surrounded it with the vocabulary of death. I am not sure childhood needed that much fear, but I do miss the seriousness it gave to small places. There was a time when a brick box behind a parade of shops could feel like the edge of the known world.

Microsoft's new MAI release reads like a product announcement until the list gets long enough to become strategy. Seven in-house models, announced at Build on 2 June: reasoning, coding, image, voice, transcription, and the faster variants that make the whole thing feel less like a research shelf and more like plumbing for Microsoft products.

The headline model is MAI-Thinking-1, which Microsoft describes as its flagship reasoning model. The company also named MAI-Code-1-Flash, MAI-Image-2.5, MAI Transcribe-1.5, MAI-Voice-2, and MAI-Voice-2-Flash. CNET's coverage notes the visible product hooks already forming around the image model: PowerPoint, Foundry, and a rollout into OneDrive. That matters because Microsoft rarely needs a model to be glamorous. It needs the model to sit inside work people already cannot escape.

I wrote in April that Microsoft's first MAI models were built, not borrowed, but they were still diplomatic: transcription, voice, image. Useful, impressive, and carefully adjacent to OpenAI's core text-model territory. This week's release steps closer to the centre. A reasoning model and a GitHub-optimised coding model are not decorative side projects. They are the places where Microsoft has been most publicly dependent on somebody else's frontier work.

The OpenAI relationship can still be strong. Microsoft has spent too much money and political capital on that partnership to pretend otherwise. However, the old story was simple enough for a slide: OpenAI supplied the frontier model, Microsoft supplied the enterprise channels, Windows, Office, GitHub, security, compliance, procurement, all the boring gates where software actually gets bought.

That story is no longer clean.

Axios framed the announcement around Scout, a personal agent built on OpenClaw, and MAI-Thinking-1 as proof that Microsoft is serious in AI beyond OpenAI. The phrasing is blunt but fair. Microsoft's Build post puts the same idea in more corporate language: ubiquitous intelligence, Work IQ, Foundry IQ, Web IQ, Windows as an agent-native runtime, Microsoft Execution Containers. A lot of names, some of them ugly. Beneath them is the same decision: do not leave the model layer empty.

This is the part I find more interesting than the model scores. Microsoft is not only trying to catch up on benchmarks. It is deciding where dependence is acceptable. If PowerPoint needs an image model, use MAI-Image-2.5. If OneDrive needs editing or generation, keep it inside the house. If GitHub needs a coding model tuned for its own workflows, build one close to the product surface. If Windows is going to become an agent runtime, then Microsoft needs models it can schedule, price, route, audit, and degrade without asking San Francisco for permission.

There is a small comedy in the name MAI-Thinking-1. It sounds temporary, like a folder someone meant to rename before the demo. Yet that roughness is part of the signal. Microsoft is not waiting until the line looks elegant. It is shipping enough pieces that the dependency graph starts to change in public.

The open question is not whether these models beat OpenAI's best models. They probably do not, at least not across the full spread of tasks that matter. The sharper question is whether they are good enough for the layers Microsoft controls. Good enough for a meeting summary, good enough for a PowerPoint revision, good enough for a GitHub coding loop, good enough to make Azure Foundry feel less like a wrapper around other people's intelligence.

Microsoft can keep saying the OpenAI partnership is strong, and that may be true in the narrow contractual sense. However, seven in-house models change the shape of the sentence. A partner with its own reasoning, coding, image, voice, and transcription stack is not merely a distribution channel. It is a company rehearsing life after dependence, even if it never has to say that out loud.

Anthropic's new cyber-abuse post is less alarming for its biggest numbers than for a small taxonomic failure. The company mapped a year's worth of banned malicious-use accounts against MITRE ATT&CK, the security world's familiar grid of tactics and techniques, and found places where the grid simply doesn't name what is happening.

That sounds dry until you remember what ATT&CK is for. It gives defenders a shared language. Initial access, privilege escalation, lateral movement, command and control: the point is not literary precision, but operational agreement. If everyone can point to the same box, the incident becomes easier to describe, compare, detect, and rehearse. The box does work.

Anthropic says it looked at 832 accounts banned for malicious cyber activity between March 2025 and March 2026. Malware writing appeared in 560 of them. Lateral movement appeared in 54. The companion analysis from Anthropic's Frontier Red Team puts the wider set at 13,873 observations across 482 unique techniques and all 14 ATT&CK tactics. That is a lot of apparently ordinary bad behaviour, and the ordinary part matters. Most abuse is not cinematic. It is scripts, prompts, retries, payloads, scaffolding, small accelerations.

However, the awkward phrase in Anthropic's post is that ATT&CK "does not fully capture" AI-enabled behaviour. Their sharper example is agentic orchestration: a model not just helping with one step, but coordinating a sequence, choosing tools, interpreting the result, and deciding where to pivot next. Anthropic's red-team write-up puts it more bluntly: there is no ATT&CK ID for that.

I don't read that as a knock on MITRE. Old maps fail first at the edge of new terrain. The unnerving part is not that attackers are using models to write malware. Security teams already knew that was coming. The sharper problem is that the old map starts to lie by omission once the model is deciding what the next move should be.

This is where the story folds back into Claude Mythos and Project Glasswing. Anthropic has spent the week arguing, in effect, that powerful cyber-capable models have to be put near defenders before attackers get the same class of help. The Glasswing expansion gives vetted organisations access to Mythos in power, water, healthcare, communications, hardware, and other sensitive sectors. The MITRE post explains why that argument is not only about finding more bugs. It is about updating the conceptual equipment before the incidents arrive faster than the language.

The rise in Anthropic's own risk scoring is the least poetic version of the same point. Medium-or-higher risk activity rose from roughly 33 percent to 56 percent across the period the red team studied. I am suspicious of any single metric in security because the counting method always carries a worldview, but this one is useful as a signal of motion. The abuse is not merely more frequent. It is becoming more capable in the places where capability changes the work: persistence, sequencing, adaptation.

The AI-worm research published this week gives the idea a harder edge. A team from the University of Toronto, the University of Cambridge, and others described agents that generate tailored attack strategies for each target in a testbed of Linux, Windows, and IoT devices. Gizmodo's account says the prototype could dynamically detect device-specific flaws and propagate with varied tactics, although it was slower than traditional worms in the isolated network. Five days to reach half a test network is not science fiction speed. It is also not comforting.

What bothers me is the silence of it. Not stealth, exactly. Silence as an interface condition. The old image of a cyber incident still has a human at a keyboard somewhere, perhaps tired, perhaps competent, walking a path through a system. Agentic abuse changes the texture. The operator may become less like a driver and more like someone setting a machine loose with preferences.

That is why the missing box matters. A taxonomy is not a defence, but it tells defenders what kind of thing they think they are defending against. If the model is doing orchestration, adaptation, and real-time choice, then "malware writing" is too small a label. It names the artefact, not the behaviour. It is like describing a burglar as a person who manufactures lock picks, then forgetting to mention the walk through the building.

Anthropic's IPO filing made the company look newly public-facing, even before any public prospectus exists. This work pushes in the other direction, toward the older, stranger role of a lab naming a danger before the rest of the industry has stable grammar for it. I trust that role only partly. Private labs are not neutral cartographers. Still, sometimes the map has to change because the road has already moved under it.

MiniMax has put a million-token context window back on the table, but this time the interesting part is not the size by itself. We have had large windows before, usually presented like luxury architecture: a bigger room, a longer table, more space for the transcript, the codebase, the PDF nobody wants to read properly. M3 arrives with a different implication. The window is large because the model is being sold as an operating surface for agents.

The official M3 announcement dates the release to 31 May and describes the model as natively multimodal, with image and video input, desktop-computer operation, coding work, and agentic benchmarks in the same paragraph. The API docs list MiniMax-M3 with a 1,000,000-token context window and describe it for agentic reasoning, tool use, coding, and long-context tasks. A big window used to sound like a special room. MiniMax is treating it as ordinary plumbing.

That is a shift worth taking seriously even if some of the claims still need the usual independent patience. WinBuzzer's coverage notes the same broad shape: frontier coding, a 1M-token context window, native multimodal processing, OpenAI-compatible endpoints, and promised weights within ten days. MiniMax's own benchmark sheet gives M3 59.0% on SWE-Bench Pro, 66.0% on Terminal-Bench 2.1, and 74.2% on MCP Atlas. Those are not tiny decorative numbers. They are a statement about where the company thinks model comparison has moved: not only chat quality, but whether the thing can sit inside a messy software loop and keep working.

I wrote in February about MiniMax's M2.5 pricing, where the unsettling detail was not just that the model was good, but that it made the premium on closed American systems look less inevitable. M3 pushes the argument into a slightly different place. Cheap capability was one pressure point. Cheap memory, cheap tool use, and cheap multimodal context are another. If those three move together, the product category changes under everyone's feet.

There is also the China question, because pretending it is separate would be odd. The recent export-control fight around Chinese AI subsidiaries is about compute access, ownership, and the routes by which restricted chips can still reach useful work. A model like M3 does not dissolve that problem. However, it does make the software side harder to dismiss as merely catching up. The pressure is not only on hardware supply. It is on the story Western labs tell about why their closed stacks deserve the margin.

The promised open weights matter here, assuming MiniMax ships them on the stated timetable. An API-only model can be impressive and still remain a service. Open weights make the claim travel. Developers can test it in awkward conditions, not only in the neat corridor of a launch blog. They can find out whether the million-token window is useful, whether the agentic scores survive real projects, whether multimodal input becomes anything more than a checkbox.

The danger is getting hypnotised by the number. A million tokens sounds decisive until you have watched a model lose the thread inside a smaller space. Context is capacity, not judgement. Still, capacity changes behaviour. Teams stop chopping tasks into little offerings. They paste the logs, the repo, the spec, the screenshot, the old decision memo. They ask the model to live with the mess instead of pretending the mess can be summarised away.

That may be M3's actual news. Not a new throne on the leaderboard, not another launch-week chart, but a reminder that the cost of room is falling. Once room gets cheap, people use more of it, and the systems built around scarcity start to look strangely ceremonial.

Gianni Versace's Spring 1991 show has a strange advantage over many louder fashion moments from the same period: you can understand it from a distance. The Marilyn faces, the James Dean faces, the colour, the hard outlines, the almost impolite clarity of the image. It doesn't need an explanatory caption before it starts working on you.

That was not the same as being simple. Vogue dates the collection to October 7, 1990, in Milan, and its archive notes how wide Versace's art net was that season: Sonia Delaunay, Victor Vasarely, Russian Constructivists, Vogue covers, Pop culture, all dragged into the same bright room. He gave Vogue the useful sentence himself: "To use art in a flat way, without creative intervention, is in bad taste." I like the defensiveness of that line. It admits the danger. It also tells you he knew exactly where the charge was.

The Warhol-derived Marilyn Monroe and James Dean prints could easily have been a stunt, the kind of museum-shop cleverness that ages before the hanger cools. Instead they became one of the clearest images of the supermodel decade, not because the references were rarefied, but because they were already public. Versace did not borrow Pop Art to look clever. He used it because fame had become material.

That is where the collection sits beside the house's other early-nineties arguments. I wrote about the March 1991 finale as a runway event that made the models feel inseparable from the collection, and about the backstage engineering of a later Versace season in Eight Hands to Get Dressed. Spring 1991 is the print version of the same instinct. The runway isn't merely showing clothes. It is laundering mass imagery through the body until the image looks newly expensive.

The Met's record for a Gianni Versace evening dress from Spring/Summer 1991 is almost comically dry by comparison: silk, glass, gift of Gianni Versace, 1993, Costume Institute object number 1993.52.4. Museum language does that. It turns a screaming dress into catalogue grammar. However, the dryness helps. It reminds me that this was not just a memorable runway photograph drifting around Pinterest; it was an object with weight, material, donor history, and a place in an institutional archive.

Christie's gives the other afterlife. A Gianni Versace Couture suit from the same Spring/Summer 1991 moment, allover Marilyn Monroe and James Dean imagery, with rhinestone and silk embroidery trimming the jacket pockets, sold in the Elizabeth Taylor sale in 2011 for $20,000. That detail feels exactly right. The thing moved from runway to celebrity wardrobe to auction lot, and each stage made the original idea more literal. Fame wearing fame, then fame sold as provenance.

I am wary of calling the collection a collaboration with Warhol, since the interesting part is not a neat artist-designer partnership anyway. The interesting part is how Versace understood repetition. Warhol had already made the famous face into a mechanically repeatable surface. Versace put that surface back onto a moving famous body, and the loop became almost too perfect: Marilyn, Dean, Naomi, Gianni, Taylor, Donatella reissuing the prints in 2018 at the Milan Triennale, the archive learning to sell its own shock back to itself.

Some clothes become historical because they solve a construction problem. Others because they catch a social one before it has proper language. Spring 1991 did the second. It recognised that glamour no longer needed to pretend it was separate from media saturation. The dress could be the magazine, the model, the artwork, the souvenir, and the advertisement in one go. Too much, probably. That was the point.

LaserDisc did not make films interactive. It made them addressable. That is a smaller claim, and probably a more interesting one, because so much of modern viewing now depends on the idea that a moving image is not only watched but indexed, searched, paused, sampled, resumed, and dragged around by its spine.

The format arrived in the United States as MCA DiscoVision in 1978, then moved into the LaserVision and LaserDisc names around 1980. It looked absurdly physical by later standards: a 30cm optical platter, roughly the size of an LP, with a video signal laid onto a surface that had to be handled with the wary ceremony of something expensive. Yet its strangest legacy is not the disc itself. It is the numbering.

LaserDisc had two basic personalities. CLV, or Constant Linear Velocity, gave you about an hour per side on a 12-inch disc. The player slowed the rotation as the laser moved outward, from 1800 rpm near the inside to around 600 rpm near the edge, keeping the read speed steady. CAV, or Constant Angular Velocity, kept the disc spinning at 1800 rpm and gave you only about 30 minutes per side, but in return it exposed the film as a sequence of reachable images. Still frame, slow motion, forward and backward stepping, repeat playback, fast track: these were not decorative features. They were a different contract with time.

That distinction matters because CLV did not contain image numbers in the same way. It was the sensible format for watching a feature without getting up quite so often. CAV was wasteful, fussy, and wonderful. It treated the film as a numbered object. A remote control with a keypad could become a little index machine, and the film stopped being a tape you dragged through by friction. It became a thing you could summon by address.

I don't want to overstate it. LaserDisc menus were not DVD menus in waiting, fully formed and merely waiting for the plastics to shrink. LaserDisc was cruder and, in places, freer. The number went in. The player went there.

There is something bracing about that directness. We tend to remember the DVD era as the moment home video became navigable, but LaserDisc had already taught collectors, schools, museums, and people with too much patience that video could be handled as an archive. Not metaphorically, either. A CAV side was a set of frames with addresses. The tradeoff was visible in the object: half the running time, more sides, more interruptions, a machine asking you to care about its internal method.

That is the bit that survived. Not LaserDisc as a consumer format, because it never became cheap or convenient enough to win the room. What survived was the expectation that images should answer to us. Click a chapter. Scrub a bar. Pause a stream and expect the frame to wait without tearing itself into noise. The floppy save icon kept the outline of a dead storage medium on every toolbar. LaserDisc left a less visible fossil: the assumption that moving pictures have coordinates.

Streaming has made that assumption feel natural, almost beneath notice. The interface is cleaner now, which means the machinery has become harder to see. No one has to choose CAV and lose half a side of capacity just to get a clean still. No one listens for the player to hunt across a vast silver disc. The frame arrives because of buffers, codecs, manifests, caches, and a progress bar that pretends all of this is just a line.

Maybe the old nuisance was useful. A LaserDisc player made the compromise legible. If you wanted proper access to the image, you paid in minutes, sides, shelf space, and the ridiculous dignity of standing up halfway through a film to turn over the future.