Opinion The IT industry is not only full of sharks, it has shark nature itself. It must keep moving forward to survive. Not all sharks are obligate ram ventilators, and not all IT changes all the time, but without innovation the sector would curdle and die.

Venture capitalists and cash-rich tech companies feel this most keenly, which is why they swarm like makos to the bleeding edge. But innovation itself is not enough. Blockchain is very clever, but has made the world a nastier place while losing a lot of people a lot of money. AI’s trajectory from wait-and-see could just as easily go that way as any other. Actual change, innovation that sticks around and becomes part of a better way forward, doesn’t have to and really should not make its inventors billionaires. It is thus often invisible when leadership is measured in dollars. Nonetheless, it matters to billions.

A much more fruitful filter for the future can be stolen from nature. Evolution by selection and descent, the theory of everything for biology, is at once a living demonstration of successful innovation and a morbid library of its failures. It is both tautologically simple — survival of the fittest — and breathtakingly complex in the interplay of environmental factors, selection pressures, and the interplay of change and stasis. It’s not random mutation until something clicks, it’s if and how organisms can change to match a changing environment. In IT, it’s what makes best use of a change in the landscape, which itself is changing as new tech is taken up.

Fork that: Three alternative kernels show devs don't need Linux [1]READ MORE

To analyze this, selection pressures are particularly useful. Take a look at what’s going on in and around the peculiar speciation in and around the Linux kernel. There are clearly pressures here from the changing environment outside it. New and updated CPU architectures, evolving models of security, performance expectation in different use cases as sectors rise and fall in importance. Energy efficiency in many different ways. All are pushes for change across the kernel.

Other factors are more subtle and with very different dynamics. The commercial and personal motivations to be involved, the talent pool available to power change vectors, the power exchange between closed and open, the accuracy of perception and the anatomy of persuasion. These are as much social as technical.

[2]

Apply this model of selection pressures to our overview of three microkernels in the Linux context, and you can see that viable mutations are generally Rustafarian - personal motivation and skill sets are changing in that direction. Rust has itself evolved in response to those selection pressures, so selection pressure will favor those entities that can evolve to embrace it more easily. Mainstream Linux, with its very high institutional inertia about maintainers, leaves opportunities to the smaller, more nimble. All of the microkernels here have different focuses, different priorities, and the art of predicting their future success is in matching each focus to the imperatives of reality.

[3]

[4]

What will really make a difference is when an architectural concept offers a path to exploit an environmental aspect that’s unavailable to, or even toxic for, existing creatures. The evolution of photosynthesis produced unprecedented energy for cyanobacteria, while producing atmospheric oxygen that was poison for many other species. The evolution of metabolisms to use that oxygen completed the [5]planetary reset event , and there was all those tasty cyanobacteria to eat.

The equivalent in IT is fixing security, which is currently so toxic that in the UK, there is talk of Covid-level responses to [6]keep entire supply chains alive following a single incident. Information theft, system infiltration, and ransomware are increasingly seen as unavoidable, with corporate fatalism tending towards survivalism. That’s not tenable in an increasingly antagonistic world. Microkernels may not seem to have much to do with ransomware, but take a step back and ask at what point mutation could lead to an inherently resilient data processing environment.

[7]

Nature uses diversity and redundancy to enhance resiliency, at all levels from ecosystem to immune system. Imagine those as primary design features of the stack - or stacks. In avionics and other safety critical systems, diversity and redundancy means parallel independent systems performing the same tasks in different ways while cross-checking each other. Building a microkernel that supported the low-level system aspects of that while also doing the primary tasks of functional IT sounds like a very worthwhile experiment.

[8]The plan for Linux after Torvalds has a kernel of truth: There isn't one

[9]Windows 11 is a minefield of micro-aggressions in the shipping lane of progress

[10]Torvalds' typing taste test touches tactile tragedy

[11]Time to make C the COBOL of this century

[12]Upgrading Linux with Rust looks like a new challenge. It's one of our oldest

Doing another that runs on different hardware would also be important. These can start as only open source can, as step modifications of existing code and ideas, building tiny proof of concepts into running systems and encouraging others to start on their own paths.

Nature has created and tested billions of years of evolution, and what magnificence has appeared. But we have goals and a sense of purpose, entirely lacking in natural selection. Artificial selection can achieve in years what may never happen naturally. We can use the same tools as nature but to build towards what we need.

We absolutely do not need [13]$300 billion fantasy AI megaclouds in pursuit of making the world's first half-trillionaire. We absolutely do not need an IT infrastructure so shaky that a handful of god knows who can wreck sectors at will.

Understanding the big picture behind the little evolutions in open source can get us where we need to be. Evolved to live on dry land, away from the sharks. All of them. ®

Get our [14]Tech Resources



[1] https://www.theregister.com/2025/09/12/three_new_microkernels/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aNFylQvOs6IAlaXsZCca-gAAABc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aNFylQvOs6IAlaXsZCca-gAAABc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aNFylQvOs6IAlaXsZCca-gAAABc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[5] https://www.lboro.ac.uk/media-centre/press-releases/2023/october/cyanobacteria-formation-explained-marco-mazza/

[6] https://www.theregister.com/2025/09/15/covidstyle_furlough_schemes_for_jlr/

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aNFylQvOs6IAlaXsZCca-gAAABc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[8] https://www.theregister.com/2025/08/14/the_plan_for_linux_after/

[9] https://www.theregister.com/2025/07/28/windows_11_is_a_minefield/

[10] https://www.theregister.com/2025/05/20/torvalds_typing_taste_test_touches/

[11] https://www.theregister.com/2025/02/18/c_opinion/

[12] https://www.theregister.com/2024/09/09/opinion_column_rust_linux/

[13] https://www.theregister.com/2025/09/15/oracle_spending_shares_opinion/

[14] https://whitepapers.theregister.com/