7 web dev trends on our radar
Experts weigh in on GraphQL, machine learning, React, micro-frontends, and other trends that will shape web development.
Independent perspectives on the state of business and technology.
Experts weigh in on GraphQL, machine learning, React, micro-frontends, and other trends that will shape web development.
From artificial intelligence to serverless to Kubernetes, here’s what's on our radar.
O’Reilly authors and instructors explore the near-term future of popular and growing programming languages.
How new developments in automation, machine deception, hardware, and more will shape AI.
Technological change often happens gradually, then suddenly. Tim O'Reilly explores the areas poised for sudden shifts.
From infrastructure to tools to training, Ben Lorica looks at what’s ahead for data.
Our bad AI could be the best tool we have for understanding how to be better people.
The World Economic Forum’s 2018 jobs report limits research to a narrow range of the workforce.
The economy we want to build must recognize increasing the value to and for humans as the goal.
HTTPS "everywhere" means everywhere—not just the login page, or the page where you accept donations. Everything.
General intelligence or creativity can only be properly imagined if we peel away the layers of abstractions.
Tim O'Reilly looks at how we can extend the values and practices of open source in the age of AI, big data, and cloud computing.
It’s easy to imagine an AI winning a game of Go, but can you imagine an AI wanting to play a game of Go?
We need to build organizations that are self-critical and avoid corporate self-deception.
Demanding and building a social network that serves us and enables free speech, rather than serving a business metric that amplifies noise, is the way to end the farce.
The web was never supposed to be a few walled gardens of concentrated content owned by a few major publishers; it was supposed to be a cacophony of different sites and voices.
In the software world, we’re often ignorant of the harms we do because we don’t understand what we’re working with.
Publishers need to take responsibility for code they run on my systems.