Software-driven obsolescence feels different because it is not merely the old story of tools wearing out. A hammer rusts. A car engine fails. A building decays. These are material limits, and human beings have lived with them forever. We understand decay when it comes from friction, weather, fatigue, corrosion, entropy.

But software obsolescence is stranger.

It is not always the object that fails. Often the object remains physically intact. The laptop still powers on. The phone screen still glows. The printer still prints. The tractor still turns over. The car still drives. Yet some invisible layer withdraws permission. The operating system no longer updates. The certificate expires. The app drops support. The cloud endpoint vanishes. The driver is no longer signed. The vendor moves the feature behind a subscription. The device is not dead in matter, but dead in relation.

That is the historical novelty.

This may be the first human generation to experience obsolescence as a software event rather than a physical one. We are watching objects lose usefulness not because their atoms failed, but because their dependencies changed.

A previous generation could inherit tools. A sewing machine, a radio, a bike, a watch, a diesel engine, a set of chisels. Even when repair was needed, the failure was local and intelligible. You could point at the worn gear, the split belt, the burned-out valve, the cracked solder joint.

Now the failure is often elsewhere. It lives in an account system, an API, a licensing server, a remote firmware policy, a cryptographic trust chain, an app-store rule, a region lock, or a corporate decision made after acquisition.

The object becomes a hostage to a stack.

The Compression

The shock is not only that things become obsolete. It is the speed.

Industrial obsolescence was measured in decades. Consumer-electronics obsolescence compressed that into years. Software has compressed it again, sometimes into months, weeks, or even a single update.

A device can be functional in the morning and degraded by evening because a service changed terms. A workflow can vanish because an application “improved.” A business can wake up to discover that the platform it depended on has deprecated an integration. A whole community can lose access to a tool because the authentication layer changed.

This is obsolescence without visible ageing.

That is why it feels uncanny. We are used to time leaving marks. Rust, dust, scratches, noise, heat, fatigue. Software erases that sensory contract. The object looks young while its usefulness has been silently aged by policy.

The human nervous system has not evolved for this. We can mourn a broken chair. We can accept a dead battery. But there is something uniquely enraging about a perfectly functional device being made useless by an update, a login wall, a missing server, or a deliberately unsupported protocol.

It feels less like decay and more like betrayal.

Convergence: Everything Becomes Software

The convergence is obvious now: everything is becoming software-mediated.

Phones were first. Then televisions. Then cars. Then cameras. Then home appliances. Then locks, thermostats, medical devices, farming equipment, logistics systems, payment terminals, identity systems, education portals, government services, and even money itself.

The pattern is consistent: a formerly mechanical or local object becomes networked, account-bound, update-dependent, telemetry-producing, permissioned, and remotely governable.

The object converges into the platform.

This has advantages. Software can patch faults, add capabilities, improve safety, coordinate complexity, and scale services globally. A modern phone would be impossible without constant software evolution. Electric vehicles can improve after purchase. Medical devices can be updated. Security vulnerabilities can be fixed. Distributed systems can be hardened in real time.

So the convergence is not simply bad.

The problem is that the same mechanism that enables improvement also enables dispossession.

The update that patches can also degrade. The firmware that secures can also restrict. The cloud service that synchronizes can also surveil. The subscription that funds maintenance can also convert ownership into rental. The app ecosystem that simplifies installation can also centralize permission.

Software turns every object into an ongoing relationship.

And relationships require power analysis.

Divergence: The Object and Its Usefulness Split Apart

The great divergence is between physical durability and operational durability.

A machine can now be physically durable but operationally fragile. This is historically weird. In the old world, robustness meant strong materials, replaceable parts, and understandable mechanisms. In the software-mediated world, robustness requires maintained dependencies, open protocols, security updates, documentation, build reproducibility, legal permission, and institutional continuity.

A 30-year-old mechanical typewriter may still work. A 10-year-old smart device may be landfill because its vendor lost interest.

That divergence changes the meaning of ownership.

To own a tool used to mean: I can use it, repair it, lend it, modify it, resell it, and understand enough of it to keep it alive.

To “own” a software-defined object often means: I possess the hardware, but the vendor retains practical sovereignty over its future.

That is not ownership in the old sense. It is conditional access wrapped in consumer language.

The divergence also appears between generations.

Older people often experienced obsolescence as material decline. Younger people experience it as platform churn. They are trained to expect interfaces to mutate, archives to disappear, subscriptions to multiply, chargers to change, accounts to lock, apps to vanish, and purchased media to become unavailable.

This produces a different psychology. Less attachment. More anxiety. More acceptance of impermanence. More dependence on ecosystems. More cynicism about the word “buy.”

A generation raised inside software obsolescence does not merely own fewer durable things. It inherits fewer stable relations to things.

The Loss of Repair Culture

Repair culture depends on continuity.

You need parts. Manuals. Schematics. Skills. Time. Legal permission. Community knowledge. You need the thing to be explainable.

Software obsolescence attacks all of these at once.

The repair problem is no longer only “can I replace the part?” It becomes:

Can I get the firmware?

Can I unlock the bootloader?

Can I pair the replacement component?

Can I access diagnostics?

Can I bypass the cloud requirement?

Can I legally modify the software?

Can I rebuild the toolchain?

Can I keep the certificate chain alive?

Can I emulate the dead server?

Can I prove that I am allowed to repair the thing I bought?

This is why right-to-repair movements matter. They are not nostalgia. They are a defence of civilizational competence.

A society that cannot repair its own tools becomes dependent on whoever controls the update channel.

Obsolescence as Governance

The deeper point is that software-driven obsolescence is not just an economic phenomenon. It is governance.

When software defines what a device can do, then whoever controls the software defines the boundary of possible behaviour. That boundary can move after purchase.

This is a radical shift.

The product is no longer fixed at sale. It is governed across time. Its capacities are continuously negotiated between user, vendor, regulator, platform, payment processor, cloud provider, app store, and sometimes geopolitical authority.

The device becomes a legal-technical organism.

This is why software obsolescence feels political in a way that broken machines did not. A cracked gear does not impose terms of service. A worn bearing does not require account recovery. A dead spark plug does not delete a feature because the company changed strategy.

Software can make objects obey distant power.

What Makes This Generation Unique

This generation stands at the hinge.

It remembers durable objects, but lives inside disposable software cycles. It has grandparents who kept appliances for decades and children who may never truly own media, tools, vehicles, or even parts of their domestic environment.

It is the first generation to see the convergence of:

physical goods,

software platforms,

cloud identity,

subscriptions,

remote updates,

telemetry,

digital rights management,

app-store control,

AI-mediated interfaces,

and financial rails.

But it is also the first generation to see the divergence between:

possession and ownership,

durability and support,

repair and authorization,

purchase and license,

local function and cloud dependency,

user intention and platform permission.

That is the compressed nuance.

The future is not simply “things break faster.” It is that usefulness is being moved out of the thing and into a governed network.

The Fork Ahead

There are two possible futures.

One is a world of sealed objects, rented capabilities, mandatory accounts, disposable devices, artificial incompatibility, and update-mediated control. In that world, obsolescence becomes a business model and dependency becomes infrastructure.

The other is a world of open protocols, local-first software, reproducible builds, repairable hardware, user-held keys, long-term security maintenance, portable data, and verifiable behaviour. In that world, software can still evolve without turning every object into a leash.

The choice is not anti-software versus pro-software.

That is too simple.

The real question is: who controls the continuity of usefulness?

If the answer is only the vendor, then software-driven obsolescence becomes a quiet form of dispossession.

If the answer includes users, repairers, communities, open standards, cryptographic ownership, and verifiable systems, then software can become the opposite: a way to extend life, preserve agency, and keep tools alive beyond the business cycle of their makers.

Software-driven obsolescence feels different because it is different.

It is not decay.

It is dependency ageing faster than matter.

And this generation is the first to feel, at planetary scale, what happens when the soul of the machine is no longer inside the machine.