"The future is already here— it’s just not very evenly distributed."—William Gibson

An increasing number of people do work mediated by APIs. Self-driving cars (and trucks) work. Algorithms, big data, and programs akin to artificial intelligence are increasingly people's everyday interaction with their phones. We put general purpose computing machines (similar in principal to your laptop, smartphone, or the servers Drupal runs on) in some people's bodies, and many more of us spend a lot of time inside computers (any modern car or airplane, and many modern houses).

What does any of this have to do with Drupal?

Despite all the (genuinely real awesome) awesomeness we hear about in session after session, Drupal is still in a 2001 world in some fundamental ways. It is a site on a server. People can log in to edit text and upload files. This was a huge increase in power ten years ago for people who should not have to edit HTML or use FTP. With a little up-front help from a web developer, anyone could make updates that the whole world could see, at a domain they owned on a site they controlled. That had a touch of magic to it— more than a touch with what modules could add for the presentation of content and business-critical functionality like e-commerce. Now content management is commonplace. Meanwhile, the magic more and more comes not from a module, but from an outside service.

If our work isn't providing the value, inevitably our work will not be valued.

Sure, we can hook Drupal up to the Internet of Things or any other buzzword that comes along, but we're just an afterthought. This is not unique to Drupal; the web itself is becoming a second-class citizen of the Internet. What may be unique to Drupal is the community cohesion needed to put Free Software at the center of meeting people's needs, wants, and inchoate desires. If we don't, the experience people expect from technology will get harder and harder to provide with code we (and they) control.

Indeed, the experiences people expect, right now, frequently rely on technology that spies on them and, presently, is provided by opaque, proprietary services.

Ceding, to a consolidating cadre of corporations, control of the computers that run our jobs, cars, games, homes, conversations, and even bodies is a grave threat to life, liberty, and the pursuit of happiness. The moral case against allowing this to happen makes itself. A moral case has never been sufficient, however. I will make the business case for engaging seriously with the sort of technologies and platforms that define our present future.

This session will suggest how Drupal can become relevant to four large markets that we have bypassed (with some Drupal products providing notable exceptions that will be noted), or that have bypassed us.

For those of us building web applications, if we don't take a step back and look at what is providing value to our customers (and could-be customers), we're going to be at the mercy of those providing the APIs to what does provide that value. For those of us making small, medium-sized, and even large sites, our lunch may be eaten by SquareSpace and TheGrid.io (disclosure: Agaric is a beta customer, and is not yet impressed).

Machine-built web sites or artificial intelligence doing parts of our jobs is nothing to fear, necessarily. Drupal already has the same effect, replacing more than half the work of crafting a web site with a ready-made framework. Ideally, we're freed to work on ever more interesting and important goals.

The challenge is to use the Drupal community—our own network effect, so to speak—to coordinate partnerships and projects which will produce value with tools that belong to us all, rather than locked-down services controlled by a few.

You will leave this session with a better sense of web development and Drupal in the context of the unevenly-arrived future, and a some ideas and even a few examples for ways you can profitably be a part of building a better web, and world.